Package: deb-perl-macros Version: 0.1-3.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-3.2_all.deb Size: 2896 MD5sum: 170fb00538c4614dcf6d5f6c4d9445c0 SHA1: 14bb312396c116e9107bed22febb02584d2bb337 SHA256: f43802d1a0a2e19357222c2ccb9eef65666f83f590ebbc7999f883bd901c1b1c 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.4 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.4_all.deb Size: 55156 MD5sum: 8be73c8c6394ddfbb87d51e6ec46dc99 SHA1: cd87d91db25986d7edba0beff37a1f985eaeecc6 SHA256: c53fa04505bb22110f047ebf89e0eee8438cba3915e03bc902ae733db0336da9 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.4 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-3.4),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.4_all.deb Size: 8624 MD5sum: a751e2b3c4679f10e2b902f999e00474 SHA1: 929159b04f6fefa3a81f87bcb6275067d6d38a70 SHA256: f91c0e1e214172355bc4b163e0bd4283c61c58982fd8b59fbe600925d654c4fd 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.2 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.2_all.deb Size: 25624 MD5sum: 8d1ca511587555c7b8eb5e1399607dea SHA1: 1e996c3bbc4ba8ff1589080868ddcfc9fda70316 SHA256: 3a064bc82eae946bf429d3545537129ab6d1974b62afa3e0b3a3094ea16d94b3 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.2 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 401 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: ppc64el/liblua5-1-5_5.1.5-2.2_ppc64el.deb Size: 76864 MD5sum: 6b123d8acba0c38b35780593e5af90dd SHA1: 54b90288676fa77bb311162f1c6303b4db310270 SHA256: 4cfee7cdcf3c1a78a6f25c77b92d8d57b61774a7b9dbf85dcb6b9d1dd84cd073 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.2 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 359 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: s390x/liblua5-1-5_5.1.5-2.2_s390x.deb Size: 74664 MD5sum: db91581425496dd9d5eb296257cc60c4 SHA1: af015376d624eee23ed50c3d984b2f48ca8c7152 SHA256: 5ca36aaadd88bedc473d17fe6deb98783ee255df5f33f878582fd00ced900b25 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.2 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 749 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: armhf/liblua5-1-5_5.1.5-2.2_armhf.deb Size: 281792 MD5sum: af707c4943d4674d92ce2b3644e61389 SHA1: 238e0ac9854b9f0d7379f6696cd45713e94264ad SHA256: fa894e96e5d0f11cdf5515cc314c9bd9ae5a1de4bf4924c77cad16d474d8bd93 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.2 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 862 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: arm64/liblua5-1-5_5.1.5-2.2_arm64.deb Size: 294232 MD5sum: 0c5c92ad406d841c7cd40e4b434efa02 SHA1: 04b28a7ea1d921e9f82d68d4c83ad06582589216 SHA256: fc910bd3c7e9d1be8fb20104eb1a369da9e74cb4ec7cce510722562419e05ab2 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: amd64/liblua5-1-5_5.1.5-2.2_amd64.deb Size: 307544 MD5sum: 0ff602ea35951deaa721e20277f4ae79 SHA1: 728e50255b0d31e3605f38ffba2774f3894d76bb SHA256: 3b9dbe7d2c89fb938ccceb2ed6dde2eec36869ad656c6bb6ebd5493dd7b7bc51 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.2 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 804 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.2) Provides: lua51-libs (= 5.1.5-2.2),liblua5-1 (= 5.1.5-2.2) Filename: i386/liblua5-1-5_5.1.5-2.2_i386.deb Size: 305636 MD5sum: 89a0ab44cd3211ec5839cda6cd03e54c SHA1: 129b5b96ba7600fb8df8d7e8de61eb1669029a46 SHA256: 0cc8a3d20cc16fea0565a1ef9a0125131bc8f6c9a7369857803bad3fa25772b6 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 25 Depends: pkg-config Filename: all/lua-macros_20210827-3.2_all.deb Size: 1724 MD5sum: f04fa7d7ee1ba13ab08cb7c6e45addc6 SHA1: fed00f6ac3f2ae803dc9cf8c0679c427672f8ef1 SHA256: ba4f06eb88ab422b63ffeae1f18e5ad25fd74a6750b839ccb75baa3946f53c9b 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.2 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 645 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-2.2_ppc64el.deb Size: 92036 MD5sum: cf514067c588226502b4aa3dbfc64687 SHA1: b4f1bb0a8061e7a8fc506a7599725e420ef49e7e SHA256: c78389d4906feba0cefb5fe3a800e7713aa840f705017b620dffdf2c2865a411 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.2 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 604 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-2.2_s390x.deb Size: 89864 MD5sum: a13e77af65d904cc90e1a1855824a7e0 SHA1: 2d44a7b23881d1b3799fa9aac5d4522ed4c1c4b0 SHA256: 5e5e612c044f429fe903a80049fec21065fba5b56ad2f0e77628666afbb68ef4 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.2 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1314 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-2.2_armhf.deb Size: 344944 MD5sum: a3fa1911d00a92cc4202c99c49341b31 SHA1: 6892cb633832c6cd4899b6d9e23972f833e9d74f SHA256: 96213ce8a3ae9346cfa27344703f8a4927111e318fd935108f8b6d43def58c41 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.2 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1510 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-2.2_arm64.deb Size: 360148 MD5sum: e0cb87ec262983850298ad2f87629335 SHA1: 92b16213171fa17a5afd10524e6f2734ddc23aa5 SHA256: a85d314d8935aa8df1f380001d2d06a0876a1d98fd3100cec10052c470aa7956 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1489 Depends: dpkg,libreadline8,libc6,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-2.2_amd64.deb Size: 376688 MD5sum: 91338d398b27f85695ff54a1ae34d464 SHA1: 2c4985eaa1a24e73fd224ccd43c50327ec01ac84 SHA256: 50f70bbc30775cf9d448f1aa8a558faab64e0fbf723042d9475520d8b81189ba 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.2 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1413 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-2.2),lua-api (= 5.1) Filename: i386/lua51_5.1.5-2.2_i386.deb Size: 374168 MD5sum: c6163ccc1a7a9a17cd985f5920ceb4d7 SHA1: 7dc57c45c6118bd2010cd95b4302e970a6257fe7 SHA256: 3fed06e44ddb88a2d41949d770016a5b8ea371aa7364a554c7df616c66336792 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.2 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 583 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: ppc64el/lua51-devel_5.1.5-2.2_ppc64el.deb Size: 93060 MD5sum: 205c364813aa101fc4bb09d3688a3eb5 SHA1: 7eeebbfb84e136167af39407bde7a264dfdf8908 SHA256: 56bfb94948bc7345b27b665b932388e08496b56aa45bb3c126350b95ded3fe7a 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.2 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 561 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: s390x/lua51-devel_5.1.5-2.2_s390x.deb Size: 90292 MD5sum: f53a0d57f932be0aee46c1bef976d1f4 SHA1: 0a68136404c52277d1eae019e0f003e279a8712c SHA256: 6826cafbcb72c8434983ee050e638e9b3377d9a402af5d306cceda9fa9b0f44b 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.2 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1109 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: armhf/lua51-devel_5.1.5-2.2_armhf.deb Size: 356652 MD5sum: 77fe6c8854d263788cbfb8707bb86474 SHA1: 7bcab70b727b400d3f29848c4d9f7748f28e09e0 SHA256: c2ff561b505b5460a1a6ca903a2d3f2e7b9449e626b674a0beda7610ad5d1911 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.2 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1662 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: arm64/lua51-devel_5.1.5-2.2_arm64.deb Size: 372292 MD5sum: 3e1d76fd6531edb6b6f10489986b3c42 SHA1: a3e1977db0072b1e0c4972c0f90e234978571942 SHA256: 1643a2f958dc37d5a4a90e302e71f6df5034e3ff83e97c918e9a723d6414eb17 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1685 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: amd64/lua51-devel_5.1.5-2.2_amd64.deb Size: 383392 MD5sum: ae24da84a060ffdc952e57601a77cd25 SHA1: beaaa58cd1ab9f77f9dc395b685a4b7c16a66836 SHA256: 57dd683f41f29f042d1220613c15b215354e40448bb124f9dcf873cb1fb7177d 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.2 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1190 Depends: liblua5-1-5 (= 5.1.5-2.2),lua51 (= 5.1.5-2.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.2) Filename: i386/lua51-devel_5.1.5-2.2_i386.deb Size: 381980 MD5sum: 38802013f63aee2d9273d54545241a86 SHA1: 2c4ea4179f8d755e3aaa3e87cd380f11721ea109 SHA256: 6442546956122ac32a2c46343cb98f9c678ab11d1c1458497480ba1329f09f7e 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-2.2_all.deb Size: 71672 MD5sum: 9252a8abc9a111adedde0f17b71f6ec6 SHA1: f463d890c88749663a5f7c82f570013d39e7902d SHA256: c1de129f25edec4dd7758edb2eb4b00bba7f1df1efc926839643c8649caf6d8c 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-4.3_all.deb Size: 30008 MD5sum: 21e957c9cb57b93b99c4cb0162df3191 SHA1: fd95dbe452a31f772415e818e0dd8fea802f993c SHA256: d6ec71647efeb30bfc14021821f44d9e06e01f87ee88a8294af42bac33ececc2 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-4.3_all.deb Size: 22672 MD5sum: 6f897cfe2b2970917b5c0684c90759fb SHA1: 7749b2df50445447ac6cc0332b1b38411dec53c5 SHA256: 33a7a6a0b471780234be38fcbf7dab26ff99dbaf33ececc7856eda3dce7d5197 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-4.3_all.deb Size: 7232 MD5sum: d1363d69e898604e3399f5a3ab6375fb SHA1: 1b1d277151be81e9c39298b3b9ba3c783450ee84 SHA256: e2acc1eed7ab6a76371bd9e9a3ebea7acd0043f51bd4c219908a88ee2c655383 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-4.3_all.deb Size: 28392 MD5sum: fbcd0970c580c717ab54fd01d5b1e565 SHA1: 3409a37bce4d21c5cbd47222c0cd0961038b38c2 SHA256: 49975b6af4c5597803d693ac3ca308ea64ce6bd26df528f30c19f1e848055ff8 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-4.3_all.deb Size: 14372 MD5sum: 475172770fcbc612c1d99e5f26463da7 SHA1: ace8184453f43bced1e04df3da085a6d749143e2 SHA256: a6d96ac20d9c33b01e2f18170e616870d11aaa88b6409ed12c7f94ae7025a717 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.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-4.8_all.deb Size: 39064 MD5sum: 6fbb974b58228ae38c04a0eb62f1955f SHA1: 3f5ff2a41954c65a85faf09e605f84545ca11a8f SHA256: 8d9d67b63a0f80f1975ff84fd087bc6b8c3cb0a7df2818868f55d47837c8ba64 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.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-3.8_all.deb Size: 39244 MD5sum: b196515c9528bf5db8289f4b2ef77a69 SHA1: 8a3db9e49b45845c726e0da620dddde772c14528 SHA256: 2ef35fbaa28d5317573c0220c63d4a97717836fc8d1b9fad7c1ee3d309e2dd61 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-6.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-6.2_all.deb Size: 304544 MD5sum: 2a0a3ae557f02f81f8ee90c641e4d100 SHA1: 9f7ba634056890d831e534749df654446f91ac62 SHA256: 9f36ec1e5d41cdb10da0b9177ec22c781bef3b9b3c970d323a4b3d16302f5981 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-4.3) Filename: all/perl-extutils-pkgconfig_1.160000-4.3_all.deb Size: 10564 MD5sum: 2461aa72bf6b57817f8537e9b092fedf SHA1: a355574d971f4f95f75093471257ee513cfc2af7 SHA256: 5238a336cd1053d6c902c950cfe64c4ea95f8920b51ddbe66148dbdc32e81f99 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-4.3) Filename: all/perl-file-path_2.180000-4.3_all.deb Size: 30672 MD5sum: 691dcc14284bbab60a044bfbfddf8e16 SHA1: ed2eabff8f45fc34edaef23bd3903d359eece0a0 SHA256: 40489ebb96fd7a6e7d451c43a0e2233217750219718b358ae936d3137669d16d 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-4.3_all.deb Size: 53320 MD5sum: defc1459ae51cb5ec18fdb888cb285b6 SHA1: 0d652a44fc49f380e990853d045997c57307328e SHA256: 1425538dece95ce2068f1e371061d3ebc964cfa2404c0a7b535a6464daf5e895 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-4.3_all.deb Size: 33144 MD5sum: 5efb82437a61dfd1e8979d678827fdd9 SHA1: 1b025995d8d4aaa4a817766c1bbf45c11380ef40 SHA256: be3b76429282c9da975664aa443faa1ae314dd034bcc3e4733bfcfc042a85ed7 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-4.14 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 790 Depends: perl-base,liblua5-1-5,libc6 Filename: ppc64el/perl-lua-api_0.04-4.14_ppc64el.deb Size: 177184 MD5sum: a4de248024f2417da5033b6b79e70d6a SHA1: 79ccb9007510aca4cb1955b0ac0d5ff074d84b22 SHA256: 0de2fbfb6e0344ae2f74152885d646e4f8ebcf2b58d7b3c9b2421c08ad98f604 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-4.14 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-4.14_s390x.deb Size: 168392 MD5sum: a17816812467d09a9120d6f9966b6c0a SHA1: c52629fddc317d297db57bc67ce9c5c02880a4e8 SHA256: 509ed82127858cf58760878c45396e4e060eeaf283d76c3fae11d4e3b692577f 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-4.14 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-4.14_armhf.deb Size: 170080 MD5sum: 7b0837a1524ec00d599b08262fd61951 SHA1: 302f12b641be8752597b64869cd14247b64c902a SHA256: 0e4ac2bc844a5df2dab588622484c953705d2fbff251463ce44c593b571bfaa9 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-4.14 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-4.14_arm64.deb Size: 167632 MD5sum: 5c683fe83c838ee3248d2cd77f4c93ad SHA1: 73e31fa732c3c77abe53056a4f46bfd16d401c45 SHA256: 54b007fafd2af9d2f558137c577e27f08850c0adf38bdd9ac2a0c3f1e04588f0 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-4.14 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-4.14_amd64.deb Size: 173748 MD5sum: 7db4cb3c61c87e5bd01cbf62f32905ac SHA1: 3976151e7a190a63dab9dfafd530ca4add48a0aa SHA256: 210a510337759ce8734890f2c5eb2ff6984d07a8ad6705b4934dcc06bdf227ad 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-4.14 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-4.14_i386.deb Size: 162788 MD5sum: fd7f1cb337c7798473396d95e57aaf0e SHA1: 494c61935d70205e8a1e0b38165853fa706770b0 SHA256: ca468070f85255189da6e888d9746e05d2d6fe10f8e2b46a652bc1e4cf36f038 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-6.5 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-6.5) Filename: all/perl-module-build_0.423400-6.5_all.deb Size: 251820 MD5sum: f21b7c99e77fbc1141fc5910c63b8cd9 SHA1: c627b14e66f650ab2663d83ba8f317ed489f0263 SHA256: 97398145c2dbf8884a121fc16038e5e13da07b77bc5f66037e1b2dc69dad8f86 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-4.3_all.deb Size: 29648 MD5sum: 1f7914c5a51358f5371a65f1a1e09f84 SHA1: 73be168b178164f68a36ecd6114e0dc21464fc3b SHA256: 772a9f7053f5fb5c206bc690b9f2a4cc47e5a2cac8a2eae95a2a376c81f526dd 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.20 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-4.20_all.deb Size: 18452 MD5sum: 6c3973baf18deb4b7c4fec17bf9b0f30 SHA1: 40cff7cc551982101be44b5b367851c94c59ec86 SHA256: bda818495b4754a1bd375ad584f75b0061616ad32b420c5b463888e48e0c12a5 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-4.3_all.deb Size: 17196 MD5sum: 0d3ad5d79e319fdf051f3e6726a54dee SHA1: ccd344de0080d81307063480e951c0fab3d20f7d SHA256: 1cc8fc970854d610b763998c4af4d7b79e34d1d9ae81cff244d309bf616b325b 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-parent_0.241-2.3_all.deb Size: 8872 MD5sum: bdc01741c055eb0bbc39252dad9b9c2c SHA1: 8c4c40000ea3eb4744af02d3f0616173c7f85475 SHA256: 04cdb347de33c9ebbd519114a6c412177c2511dd54bfe52fd325ce49e17b4d01 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-4.4_all.deb Size: 15200 MD5sum: 2ee4a9eeef2622a4a69b2b5fb3870589 SHA1: 56eb5d1e3f8f3519756dcdead858474665017334 SHA256: 1a57ad39788e6bc16e21fd60f81abc6941f36a2e178bcdea64b0705b884e23cc 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-4.5_all.deb Size: 19132 MD5sum: 24ff89ad7a045077e88c903fa506a5f3 SHA1: 5348d6a25830e675bd3776d8c5d95c1d8cab470a SHA256: 302e2757dbab12aa1f4bc9d86000d4dcd4a8b2acceff19699c4c4166c65ec1b3 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.20 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-3.20_all.deb Size: 22164 MD5sum: a921e36cd7aaa11786f802194da1c393 SHA1: 85089b1da57729b3810dced0cc01b9f5d90fe0df SHA256: 3cd351d36c0fa0d70882853e783ef13e6714fdcd5c73eda22b3f8b156f5ca39b 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.39 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.39_all.deb Size: 56796 MD5sum: 5bbb126f73fb4edff25c4c7e67b2b50c SHA1: e6cab81ebcbc18d43ee3281f638ceb9bbef55c3d SHA256: 45de57cdedb81e74ba09a31c9c5ee3b04ff439d280a26195235bc6cd0a7d1fa7 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.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-4.16),libtest-compile-internal-perl (= 3.3.1-4.16) Filename: all/perl-test-compile_3.3.1-4.16_all.deb Size: 21456 MD5sum: f4a42891ca15ad2b0d00135aa7734747 SHA1: 99e454492f9f111676731cade8d9370fed89ffdc SHA256: e29e1839733fd5d26ac009d3fecea1700814cc28380340f2c029ee6d037dcd05 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-5.7_all.deb Size: 93248 MD5sum: 0b3220728a98f24743a34dc77f1db3b7 SHA1: f972b5d9f9fa5119449822f72cbbb2000883ac74 SHA256: f35b2c48d2d01718ec65c7c056ef6d1dc80111aab69c3cf67faac683459723fc 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-4.7) Filename: all/perl-test-differences_0.710.0-4.7_all.deb Size: 18376 MD5sum: f636900d2ee970492a543824560cba7b SHA1: 149d9c6d407e63d5759e239d9b4bff4819070e7e SHA256: 0b3162c54544884cd777a0d6742a42831e01c8b6a32b83ade21a1dcb26205149 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.27 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-4.27) Filename: all/perl-test-exception_0.430000-4.27_all.deb Size: 18080 MD5sum: f47a6ebbb7e80d452e20acd3dfbd1a56 SHA1: 8451a394298e5925c0f819ea421aa325789db377 SHA256: 547d8ac807ed2118c96494f46ce08730c270658cc2e276d6ae50805e56d39ac0 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.38 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.38_all.deb Size: 23420 MD5sum: 8167f682aa2b9d0824d929bd3da256b1 SHA1: e6ef1406ef9a3ab1bb4144244e5bd2dee0052798 SHA256: 1f4787cf5dc80c319d3fd8d8e43a2dbf4e4601b7adb6f6573fc3a02cc2105284 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-4.3_all.deb Size: 13316 MD5sum: ed687acce10655fa1b9429340905f726 SHA1: 7fe4da1b3ea7d2abd6af84a8000abe490c37d757 SHA256: bd57e99285f0b624418d49235b7d8b1642f8881d3df64a594f18acf798b13d55 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.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-4.10_all.deb Size: 10932 MD5sum: afae6ab82748e5d57c92f90f815d82a6 SHA1: d782b53eef5b91b841577aa231205b4392fe558e SHA256: 02c6df9ab3d79cb7323d2f14a23830d88acf5406b1809906dfd445edc47016a0 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.27 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-4.27_all.deb Size: 14848 MD5sum: 1c8f2a64d80d5d8f3d89167f8c7a1dcf SHA1: 8c25bd0b0a19b8e0cc77f53dadc2b640a56659c2 SHA256: 540c5b524d90b20c5a805b70bfb528873f063e546b887e104586898ff1a6b20b 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-4.3_all.deb Size: 33340 MD5sum: bae0b4bafbcfbd2e56c5b6e977bbe20d SHA1: 177a158ea509bb8bfb592fac1b1875fc17a9b909 SHA256: 19827dce6c90fd137093647e4425f20013b9a9b02dbf7aa93b465621f57f8c80 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-4.3_all.deb Size: 23964 MD5sum: 20cafd9cccc00c0a8d259b70f87ee3c1 SHA1: d4c4ccb8eb7bcea8252a1f7aa8c051e4b6609cda SHA256: 5264a4b73b4150b8baf70d18ac9a5f049370a2522afb1ecaa12867d3d4c5f050 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-4.3_all.deb Size: 8920 MD5sum: cbb3894eaa2684b62cb0b7b81b798282 SHA1: 100fd10193b7fdc76e1bba5d596f7bcf39fa4538 SHA256: 2f58b669c0e727be0f801b011ad563f3756e4b1f965e2a59daae94f9436abb08 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.