Package: deb-perl-macros Version: 0.1-3.1 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-3.1_all.deb Size: 2896 MD5sum: 1d5ddea29cbc3e50f7014461c4495eaf SHA1: 9c9706148512bc45114cc7318155f4ab97b8a7e8 SHA256: 4fc241fd695226ee9d9a3d6516f096e4e0e9054c049ffb55fa39983927691879 Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-3.3 Architecture: all Maintainer: debbuild developers Installed-Size: 209 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_24.12.0-3.3_all.deb Size: 55148 MD5sum: 13d9b7ed0b72c11d4039c7a6183df876 SHA1: 08a01ae108f8b66bd5a23143631696c464c87ab1 SHA256: a467b86c1d5bf307cc06274c5ba6e54ab3003ee14613b476294fa080cb47af3f Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-3.3 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-3.3),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.3_all.deb Size: 8620 MD5sum: 4607e7f5c5328882b2fe6007defb93b3 SHA1: 9c89e22e964bb044c693430df2f59674336aa822 SHA256: 6cf809146e0be3d15d6d50bf7717ef73ea529e232d149bb5a7fa95b4d3ba43b0 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.8-4.1 Architecture: all Maintainer: debbuild developers Installed-Size: 126 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.8-4.1_all.deb Size: 25616 MD5sum: 910f2f351b69415a181564177824b313 SHA1: cde0d2c6608f74c59c86eb99ccd0b01316def8c8 SHA256: 9758966a0f3fc5e0d47564d98d3186eecacd271b4797c237f19954d3027cdb72 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 401 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: ppc64el/liblua5-1-5_5.1.5-2.1_ppc64el.deb Size: 76944 MD5sum: 2b5902388ffc9c517b323b4042fc1aaf SHA1: 710b1281a6f61034fa06ab9021a53618236befae SHA256: 177bd0d94f1960ee234fcd784300c3dcc84fe290473ac0728dfd13770d9242a9 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 359 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: s390x/liblua5-1-5_5.1.5-2.1_s390x.deb Size: 74604 MD5sum: 6f59d9da29db51c675be89c196ab064b SHA1: 67c243210427227471bd9dbc5a0fed14b1affc8e SHA256: 7b8dfdedb45dd5866e0c76064f35836d19741fb3418e59e42d719347b70ce6b3 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 749 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: armhf/liblua5-1-5_5.1.5-2.1_armhf.deb Size: 281960 MD5sum: b3e6b7e53d4835aed82919d109bab5bf SHA1: f0bbf4f663b9d8c4830f21e22754206e3788550f SHA256: c52072b5cb70a8d8683459dc8744d0c195839848ca65b5924d7d1aa54704c350 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 862 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: arm64/liblua5-1-5_5.1.5-2.1_arm64.deb Size: 294508 MD5sum: 1114e7e7ffc30331126a116c0330b386 SHA1: e6c4e4774e8151f25a387ddc094f62fd9d278f68 SHA256: 9ed80df5855802275937e0e39dcfa7b8651376f0c756fb48fa93697e35b475cc Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: amd64/liblua5-1-5_5.1.5-2.1_amd64.deb Size: 307608 MD5sum: 7b9b29b2d2709dfe12c2af29ce1bdb97 SHA1: d64b016aae6c3893bc3fcce8cab91832a265e0e1 SHA256: e8f01ed2448af852c417715efc06364e6fefeb659c15f1b9447432b37eca5be1 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 804 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: i386/liblua5-1-5_5.1.5-2.1_i386.deb Size: 305624 MD5sum: 292351665a4bb0b8370061c4369ba4f6 SHA1: aa04db5287ca5fdcc2c275e98d6698d751367713 SHA256: d8320a60970474541c997740d4f582c73f4515f002dbd506062fa22944d75a66 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 25 Depends: pkg-config Filename: all/lua-macros_20210827-3.1_all.deb Size: 1728 MD5sum: efaa8c5cd841873161cded237ea2aa3b SHA1: 28519d2f1ea31046a1b48d1a423b61b663a4bac9 SHA256: fa1de2e7ef964d098361c0945c98ea9365fc0b4c3d499363cad0a86fafecf833 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 645 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-2.1_ppc64el.deb Size: 92580 MD5sum: 8ac970c8cf6d5205b166a486d9cbd7d4 SHA1: 02ea487eb1492d18d5df0e68d7891500044747cc SHA256: eabedddec9d4bcfb0aec74bf351e43d8be771df2947d99435ee86cd02a3939c1 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 604 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-2.1_s390x.deb Size: 89780 MD5sum: 38e62929327cab481e5e1e547f146dd9 SHA1: 0647d95cb5855b29bd7e898a35f9076549a097ec SHA256: 908f1093b78ff5dbfecb1fca238df974c6dec65a37e9197f4ab2ea080de17bb4 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1314 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-2.1_armhf.deb Size: 345212 MD5sum: 695637e8e009708226c3cbbaa115071f SHA1: be40c5ac67804f7e13280bdb10ff500afbbec6f0 SHA256: b1c4e99fe77ccaa1f57a28593b9a337caa4d3bdad83845e112f33508f65fcd93 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1510 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-2.1_arm64.deb Size: 360064 MD5sum: b0d993defccfe26bfc923dfe743ba465 SHA1: e175632c932d9daa595409bb39c2d8e9bad019f0 SHA256: 83d3e8a9034f4a7540207db8e003884837614477625874c9f4a24ed956675542 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1489 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-2.1_amd64.deb Size: 376556 MD5sum: 2fb2b89ef2467bdf1312f56b89515f3b SHA1: 6d780b63f0f0011d9cd721fff4c10511d77d9dfc SHA256: 55138b1a65eabca137fa0cbcb50ff8f8a8eef83331c3a73f1ce9b32264a6a9db Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1413 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: i386/lua51_5.1.5-2.1_i386.deb Size: 374316 MD5sum: 4f043bb5f58c194e42600361fc6471f6 SHA1: c84a75c377b1f51447e38f6bb1dea350acdd408b SHA256: bfbd2219759b6d39aef2634bc2416f9ff6dc00871aee223c4e31a101322a533e Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 583 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: ppc64el/lua51-devel_5.1.5-2.1_ppc64el.deb Size: 92976 MD5sum: b5ea8064f2103c77b50cb1ccc94cec68 SHA1: ed925dad6679a971ad3d4a5282d590cd3d297197 SHA256: f45b89d6f8be210f2ccd18fda21eda15cabb415262c43f12a71e9cfd047808d7 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 561 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: s390x/lua51-devel_5.1.5-2.1_s390x.deb Size: 90312 MD5sum: 0c62321889b86c9551067221f7ff18d8 SHA1: 13bcdec74e6047b69feece4b01a77f32e00281f8 SHA256: fa58ab1458d6ea2ec4c3ebc0017a08cd4ed109138e1613fc2eea486df3b9cb94 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1109 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: armhf/lua51-devel_5.1.5-2.1_armhf.deb Size: 356372 MD5sum: 93f1565a44f82112738f1698713785f7 SHA1: 3e91887479bb9896c9e0a52452a57a72b9b73a89 SHA256: 85ab3af70e08f1a551c7090354db3f6b0271b397f217fdfaa1d0a1c126c14389 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1662 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: arm64/lua51-devel_5.1.5-2.1_arm64.deb Size: 372324 MD5sum: 1ec3d246bc984a1cba255518fe1fe82e SHA1: 5ddfa840f7d4bbd443070e1f2272320fe2161bf0 SHA256: 0026c427cfee87100d47001b3e21088789a67a6530a6ee6c8b1d41b4620cc989 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1685 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: amd64/lua51-devel_5.1.5-2.1_amd64.deb Size: 383288 MD5sum: b4d59e315e731559b3d7847c17fc7e26 SHA1: 3d899a68917411c0625c59245089d7a42857d9ab SHA256: 09f51c16d84e3434ce19cd0b072d2f0ccccb3f15efdb6ccbf77bb134ed8fcd6c Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1190 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: i386/lua51-devel_5.1.5-2.1_i386.deb Size: 382192 MD5sum: 315bf11d24959a74141a41f5dbbc8d26 SHA1: 92747fc270ee5b969886e8c113a42cb7aec70852 SHA256: cfc666822fd6cd4a836ab17fca6cdcaeeea9382667f91eb9fe557407c9cbe205 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-2.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-2.1_all.deb Size: 71656 MD5sum: de60f0c4cac5bcbc7cf59e7902315ea2 SHA1: 61c3a22447306a2b005b79fb66472d13cd6e001d SHA256: ad7f79fa9dd4f9c8493659639fc76f446dc6ba62adc735b47a07a109e6558754 Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-4.2_all.deb Size: 30004 MD5sum: 5c398f74c849d899f190d3301c8281f0 SHA1: 3e69522b1265477f023503de7ac965209a1c7cfa SHA256: 5e6e31d8ac0a49e371a2ff099fb9803c9dc30820e25d2a61e62e803b48c701a2 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-4.2_all.deb Size: 22672 MD5sum: dfaaf5531aa257db27056ab6c9e9819b SHA1: 284af3efd350f72223bacaec776d24676199c896 SHA256: 66a6c254bbe0af6af20329c64b53c99b07fe03085e0610760d0adb668e327fb8 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-4.2_all.deb Size: 7232 MD5sum: 958cd76d894c82309afeed626304b52e SHA1: 5448af6955ce2446202f1e6fb0ce34bbb2a37a80 SHA256: b1f12d599ddc36fea46cf3ba50b34e84ed2361b2997c3fb44565c60c7675fc27 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-4.2_all.deb Size: 28400 MD5sum: 6e9757e1995a751ccaa5fcf40b215b3b SHA1: a441885d8be1fef13b8bcbddb243c7eddc69e978 SHA256: d69bbfd10fbfa84c2953f3628671ac89ae7b8369040c20c0d6e0b30bfc092956 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-4.2_all.deb Size: 14376 MD5sum: 23decccc13e01158431bb32b70fd11aa SHA1: 1a45913c795b8b0b8b512c4c51439201f2d70d6e SHA256: cc2caf19f96532a20559212b39ef91540b41753a2060009e823a7ad5d232bf03 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-4.5_all.deb Size: 39044 MD5sum: c7207ffda3ebc26ec23a03758c2e2f97 SHA1: 345c317fdfc4a180b1ee33bfa3725b355945ec61 SHA256: 8ab494676d50c4ba7095aded9c85c0eda26178c38e9800b1c435d0e682e67948 Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-3.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-3.5_all.deb Size: 39248 MD5sum: 237e9a77363ec432ebbf88e239e72c59 SHA1: de022b66fdf1df45b5274d40ce78409638472895 SHA256: 3faad96f591a9c40998d9b44f0172def4acc4709f47e670c5b1be4059d8936d7 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-5.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-5.2_all.deb Size: 304524 MD5sum: 282c8bfdb00934fa3b96bae505418c19 SHA1: 100979d914dcb40d77555bb1214a5d0216f5cfc7 SHA256: 59eee96c70da102c9ce559f516fb5293247ebe8b535e69539d367012b5ccb044 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-4.2) Filename: all/perl-extutils-pkgconfig_1.160000-4.2_all.deb Size: 10552 MD5sum: f0d3d4722b57d1eed972fb1a7a1060c2 SHA1: d1d5dc51f16e902d4d5ee21220ce70d88d1520fd SHA256: 52300f514a45af38a1971999ddfd4bee45716807b5447e5e9da8f7d31b6837f1 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-4.2) Filename: all/perl-file-path_2.180000-4.2_all.deb Size: 30668 MD5sum: dd79a015ea33dcfb8a8a9b3ff502a406 SHA1: 86da80d68edc65196904c88937b8dcb7c9a1feba SHA256: 83b6340e6a60c46fa577190839a77b19885843f5d8217f722aea81581c841528 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-4.2_all.deb Size: 53324 MD5sum: 5c43e59f52fd73423087e31bb33038af SHA1: 064c15ce9ae7ca444f157cb07ca0928315e85934 SHA256: fd41eae6b5f2b5e6f53584501bb67a1e79c216a2e2d03ee2afd785950bd7728b Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-4.2_all.deb Size: 33144 MD5sum: ce04b8b0a6028e71d2e2f5abd469c0d4 SHA1: a4de0eaa72056ea2b271002cdd5f0cf6091eea48 SHA256: f543cf2cf2dc22d3284d6954551353224018763e4de8a51c5391b9bae74de725 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-3.30 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 790 Depends: perl-base,liblua5-1-5,libc6 Filename: ppc64el/perl-lua-api_0.04-3.30_ppc64el.deb Size: 177176 MD5sum: 401f177249ec7d84523b29d0aff9362a SHA1: 25a18cb5bc2b7ee0d5697253aaf06cb4b4e53881 SHA256: 6ec0ddf7857c6e538ac56470a5af3751a292f26140967f4972471de8794c5d05 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.30 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-3.30_s390x.deb Size: 167820 MD5sum: ac9eaf09cfe28481f75b8d13744cad6c SHA1: 5d19c0b3d312de6306cb60c3509091d13ce9b2f0 SHA256: dfb2b742b077da3011f86ed759752496526562475e0352cdacd4e5ef62793090 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.30 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-3.30_armhf.deb Size: 169852 MD5sum: 50fd92c741ea957b899ee111b00aab17 SHA1: dc9d7b724c02cbb32ff97a05e10440cbd2bc02d9 SHA256: 84619c6cf1d69530eb0ffdcfe0c606aa687a015f61666a6d1d08507a8d21352d Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.30 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-3.30_arm64.deb Size: 167208 MD5sum: 2c49dc4c978786aaefa5372e76fb622e SHA1: 173aca94b8436f3f1f886a7542d81ffa40f72d13 SHA256: 5938494d7d909e0a1a232fcfa168ed2cba3523481c90af06a79f136d4394312a Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.30 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-3.30_amd64.deb Size: 173932 MD5sum: d948b7b4629403cdd31cf47584fed41a SHA1: 11e6af81920aa2f73df6b551f5862efeea743c54 SHA256: 36f6b896b6c5d6ac0afd1d9814e454eb0f66805ef487ebd6b95511a21cd5b044 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.30 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-3.30_i386.deb Size: 162616 MD5sum: b43d6b5fb775efaab13b73dcb44482d1 SHA1: e112aef61df511d9b13566340a0f709e290d9f7e SHA256: ac1724a67ae4dcf9b6ad09fd160d8d6b14e512143cfc21ad0e86170515b1bc86 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-5.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 733 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423400-5.8) Filename: all/perl-module-build_0.423400-5.8_all.deb Size: 251600 MD5sum: d14446ead3eaa16f455279e52293c94e SHA1: 17746182515d94c4b076d969104417527c311eff SHA256: da7d340e11b42552621d696b8612bfa38f0ab3a337f87b2828646206a5d37d01 Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-4.2_all.deb Size: 29644 MD5sum: c0ee6703317c18d7d8000423bff710a7 SHA1: 5a980d367574de816173d4f3bfb20d5e3dc0a50f SHA256: d98e1d0d350d69a79fd65b40ea18ccc1a5daa74adc353d2af674d0ce9a314c46 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-4.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-4.13_all.deb Size: 18440 MD5sum: 17c1dec72109ac1cf4e138aaf2dfdc4f SHA1: 134fc10c40eb1cd9a817b14ace842d36f4860ff7 SHA256: 966e58c8b44eed9a0946e77370479aab06f85baedf4715be0c2ba0b94aad61fe Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-4.2_all.deb Size: 17196 MD5sum: cdc59f8999e56bb4d8cce013349dba9d SHA1: 45ecdd410dbd60423c3f17dfa698d36f1caed2cf SHA256: 3540165d809401587621596005fbf70b50cdc8424cc511f4e555e4633d2a2990 Priority: optional Homepage: https://metacpan.org/release/MRO-Compat Description: Mro::* interface compatibility for Perls < 5.9.5 The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. . This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). . It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. . If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. . Some parts of this code will work better and/or faster with Class::C3::XS installed (which is an optional prereq of Class::C3, which is in turn a prereq of this package), but it's not a requirement. . This module never exports any functions. All calls must be fully qualified with the 'mro::' prefix. . The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other useful information. Package: perl-parent Version: 0.241-2.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-parent_0.241-2.2_all.deb Size: 8876 MD5sum: a263eeebf9cd3cad9a3f9c0d68f27e9b SHA1: 7c5a9c6e19a61ead93f6c5d26a1d367378a4f0a3 SHA256: 55c3d4094017e01406c0be24388c27f424060e8b47ed25a9afb125265e45ec14 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-4.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-4.3_all.deb Size: 15192 MD5sum: 07ced3898f3a8e223bae23d24eeececf SHA1: 64cab00413984aaa32bd6260215894fcb6878915 SHA256: d95dc266e7958db7b963206d20f0804d604c822a0300e8579602179c999cd30b Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-4.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-4.3_all.deb Size: 19128 MD5sum: 2fb8199ce33a12106183cba2b57e1160 SHA1: 7e4ebc920f92e65648d18e6d8801ce5265f23389 SHA256: 0ef1f05798ef927c43fc8846c64f9dac6e6aeb564633f868a0aa7833a0668156 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-3.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-3.12_all.deb Size: 22172 MD5sum: 55627ebefdc7f9f056644fea6f6f7dc0 SHA1: 41a55b038710748b755e50557aeb15f60475e4c6 SHA256: ed35e94644b926669c3c0a0829221983eb6a00f10dd6db342be36b0b85e3d940 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-4.24 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-4.24_all.deb Size: 56812 MD5sum: a63945357ecf886c8233c9f36ba9c599 SHA1: 66c2f2b2b7057a32117be1e30ab65802538af33a SHA256: ceffae4ee7266713e12c7cbce02850629b8552f0ab54d812153701f8870e5ac5 Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-4.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-4.10),libtest-compile-internal-perl (= 3.3.1-4.10) Filename: all/perl-test-compile_3.3.1-4.10_all.deb Size: 21460 MD5sum: 7aa0432d74d6b4130f49c8c66fe2d3c5 SHA1: 600bb430b53af0d3a842efe90fdd6c1ccacce749 SHA256: 8d968c81ffb19e9f4eff61f13b5b9b9855c50f65629f0fd7ee3f80d1fb28d4f3 Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-5.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-5.4_all.deb Size: 93240 MD5sum: 65acc54b11a046314b45cef9f2bb2060 SHA1: d6ed9aafbe057a119d0dd55c9a25978f5b1cebc3 SHA256: 22d1524e2220b6678337761f48ef4cd62880d89a95f7a11ebf6577524c76efdc Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-4.5) Filename: all/perl-test-differences_0.710.0-4.5_all.deb Size: 18376 MD5sum: 6c8ffd61edc83b571891ab1feda7aeba SHA1: 2b653633e97e337f90d1ffeabdaf3c4566d2c569 SHA256: 589f74d952dca9a9384c334fa4c7613db016407e1dc34f35e50c6b07cb06e840 Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-4.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-4.16) Filename: all/perl-test-exception_0.430000-4.16_all.deb Size: 18084 MD5sum: 2fce2841d76b4a31b9daf7ead5861d4b SHA1: c79b9eb8c71e816cc091107ee8b6f9a5bd25c7a7 SHA256: d78f447d781b227bff59f9b9b7c845afeab7be31907e2ff720c010609d1964d1 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-4.22 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-4.22_all.deb Size: 23428 MD5sum: 896f0bd4c5431cedc2fcab0f49899925 SHA1: 65411da4f3070676341f26a8a6cd9a8a70602d85 SHA256: c28ac7754da46831105cb02a4621c2b5ec12892beb59243870b390baaf87ef79 Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-4.2_all.deb Size: 13316 MD5sum: ea4f574401eab1c1d51088a0b97bd7ae SHA1: 578ec558d42dfeb14628114c3ebe7c3d06128b5d SHA256: ec2f1aad6a6d013b4799686551113c50973d81cb74588e6d120c78605f76b9b7 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-4.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-4.6_all.deb Size: 10928 MD5sum: 4ba0247b305a928f23ab88ce73de8190 SHA1: a0678a8cc1b0d43d8b395736d198fd35624c2fee SHA256: a709ff6396c5884e0f4617d0dd82b6092bb46598c9159eb505c8c730e404ae50 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-4.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-4.16_all.deb Size: 14836 MD5sum: a7d1895ba38df270214891cbbe013582 SHA1: 1de852abc74ab6eea6ef1e5a8044ecfb895242ed SHA256: 3d170790691252760f958e74bc03214614549ed33e17ed63a42c8e4a53200a04 Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-4.2_all.deb Size: 33348 MD5sum: b3250af01a1cb029756344c62bed0235 SHA1: cbfe8d6789ef9c14326dbc2aa659b3e772bbb155 SHA256: 1f71ca1d2c242901647ddc5a6fb9d47a77c4da9b5dc1691f83aac48ae935ccbf Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-4.2_all.deb Size: 23968 MD5sum: c3c2b3a253840b46a544a42e130eeb4e SHA1: da08c43910dcd8443b53d3032c312ff6a3294cfc SHA256: fcad49a231858d19a431fce6ed60e7d30ccecad3e82b764e9d693a2c30bc0b86 Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-4.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-4.2_all.deb Size: 8924 MD5sum: c6f13b530a5a55cf90e07e1704a6c380 SHA1: ca9cabf227c74e34f0534574d7a5dc7f094d092e SHA256: 5679938289e6589bf8bda9bd72b57b35c677a5c0a9c4e2c1f0b9ba8b0e16002a Priority: optional Homepage: https://metacpan.org/release/UNIVERSAL-require Description: Require() modules from a variable [deprecated] Before using this module, you should look at the alternatives, some of which are listed in SEE ALSO below. . This module provides a safe mechanism for loading a module at runtime, when you have the name of the module in a variable. . If you've ever had to do this... . eval "require $module"; . to get around the bareword caveats on require(), this module is for you. It creates a universal require() class method that will work with every Perl module and its secure. So instead of doing some arcane eval() work, you can do this: . $module->require; . It doesn't save you much typing, but it'll make a lot more sense to someone who's not a ninth level Perl acolyte.