Package: deb-perl-macros Version: 0.1-2.1 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-2.1_all.deb Size: 2700 MD5sum: 14bc23ad9efa8a8e10a777cdb6ea7192 SHA1: f7807709fe60ee3638e0ce7e5426f5b99fe3a7ee SHA256: 98aa79e813f260d502240b9502d2c1bb90b0fc38f4ce072cb2c3f474468ce7bf 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.1 Architecture: all Maintainer: debbuild developers Installed-Size: 153 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.1_all.deb Size: 54900 MD5sum: 37a0ff168f289f986374946c625cec15 SHA1: 570ed4ac95e65a80978bc73a2ef4ef47ab61458d SHA256: d726fab63cdd739e87d0b8e162b1a601c9bfc21c9318c55f16258f66ac5e8d38 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.1 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-3.1),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.1_all.deb Size: 8624 MD5sum: faee9b06790c7e4558e003f5940137e0 SHA1: 28da371353f40c079d6b4eadfa00f257a406754f SHA256: a0ea775d028cc9ec38cfca56287517b62d518a7db1f836a8aaa4a8a435731c25 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-5.1 Architecture: all Maintainer: debbuild developers Installed-Size: 90 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-5.1_all.deb Size: 25628 MD5sum: e3245ea71ff6ffccfcaa252e912fef9c SHA1: 2c1db9902bd338d3a51eb795f4a7d4154abd2bee SHA256: 2c7f9cba7ad33b22e0747a8bc44ccbb8723a1c97777003dd2493672e168d39ea 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-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 327 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: s390x/liblua5-1-5_5.1.5-1.1_s390x.deb Size: 74840 MD5sum: 6c3c4f3ebb94bcde7a901fbde352c5d2 SHA1: 494504ede22c87ec8b6262476d001ae062f6095a SHA256: ee0df0d44a8bef52eb0b26ae3e9a42e4f1e7bf3e33c741a78a6ef5bf808f2b4c 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-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 839 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: arm64/liblua5-1-5_5.1.5-1.1_arm64.deb Size: 295288 MD5sum: 9beafd0376bbf53d07b9ec654e11868b SHA1: 17091d274b7a5e9bf693f70d7b9c4fc80bace9e8 SHA256: 36a3101f31e4db8ba42f1948f0e1d20fc0a099c5c5879202843137c0d6b24ac3 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-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 760 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: armhf/liblua5-1-5_5.1.5-1.1_armhf.deb Size: 284772 MD5sum: 68ac2ff332139217231abf255974f177 SHA1: 5ffd8a93653ee7c3e32ac41ea0228e69f05cb605 SHA256: e9113361b7baa9cb7b17ca5eed79cdfbd6ca1eaa83a862369992c83b2776b4c1 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-1.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 369 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: ppc64el/liblua5-1-5_5.1.5-1.1_ppc64el.deb Size: 76840 MD5sum: 2086d2ceb9469d0f5b399beed46d7a95 SHA1: 84338526d589926a592d3161bf0c0e925e67f4ca SHA256: 79b54e7f441c240c0ec598cad76ddd0ec22a5f029909052df26e718ef0b05e1d 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-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 833 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: amd64/liblua5-1-5_5.1.5-1.1_amd64.deb Size: 309924 MD5sum: 3b4f6e3558c7a50b2f38f5737966ced5 SHA1: cb5ff53fb4e61715d0108607823b0d47994c25e8 SHA256: 6fb813301cae28f57eb10fc5c487d390e9637f754ca894b634c668b2f992305b 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-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 785 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-1.1) Provides: lua51-libs (= 5.1.5-1.1),liblua5-1 (= 5.1.5-1.1) Filename: i386/liblua5-1-5_5.1.5-1.1_i386.deb Size: 306708 MD5sum: 3db746fed3120a514fa04307ba021fea SHA1: 51d0f2b592b75dfca073d68dbfa1be3868ec7a0f SHA256: c14b4ea79c0f5170abc9abe06f7d02c18af1bd7e98da4d5157d067cc215ad809 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-67.1 Architecture: all Installed-Size: 2 Depends: pkg-config Filename: all/lua-macros_20210827-67.1_all.deb Size: 1944 MD5sum: 7deb7bc1c19c0c1824c2bf76859becc9 SHA1: bc1efa6a409bafe45bc24fcaee2f91ee81589063 SHA256: 59bd9f7f000cc31ad2e5d361dd37d48b9386e431c759317e0b494f488297ccef 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-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 544 Depends: dpkg,libc6,libreadline8t64,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-1.1_s390x.deb Size: 89060 MD5sum: de7abacae0b4857fa09bdf1d2b34776c SHA1: 9df83d21beb38d557dbff31e93daa3a12a8695eb SHA256: d9cea66abb042e5288649e612ec2ac5c77d26eb62e834b65d18e2a5630745137 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-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1465 Depends: dpkg,libc6,libreadline8t64,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-1.1_arm64.deb Size: 359884 MD5sum: c54f8854212a8554608095dc3861433d SHA1: 08acd5f4731da90e6693ea72fb88aaedc2e2057c SHA256: e23cea48fd76fd065c539492345733dfff4e1bd629338c8fbd59ebe3e7717bdf 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-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1310 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-1.1_armhf.deb Size: 347656 MD5sum: 6a104350ee1493be4ffb68c3ce399b75 SHA1: 9f72a1748544910c85f2ea5961a91e20863e9808 SHA256: 55331a49b9023e23977a685498e262cbed0649bf68984f252bcb1f2d38e50f46 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-1.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 585 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-1.1_ppc64el.deb Size: 91956 MD5sum: b04f7b28cd51cafc8d74bd23b3733a2b SHA1: efed10101ce4a5ec4e892e13be61f3a380c86d4f SHA256: 6195f452d85a8ff9396ca4223fd3c07bcf397e3dd946a0bfc9979384ad692ad5 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-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1444 Depends: dpkg,libc6,libreadline8t64,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-1.1_amd64.deb Size: 378976 MD5sum: 7604ed5318b50b8ffa3e84d4818037fb SHA1: 84adb55f2020fb5dc511a3b37409b6373e784e75 SHA256: 425a7b484106102cb79d2ca2c7635a27e7b3b3dda51e5680010a812bd5089655 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-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1363 Depends: dpkg,libc6,libreadline8t64,libtinfo6 Provides: lua (= 5.1.5-1.1),lua-api (= 5.1) Filename: i386/lua51_5.1.5-1.1_i386.deb Size: 375076 MD5sum: 2a3908697bd10824d271d5b7e02da418 SHA1: 175f60d08fb67b02dbf65770a215f30bd40a4ee3 SHA256: a157bb7f21a451a1d3360ed3519df80843e8a5c18553d0e27cac340ce4d13e60 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-1.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 516 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: s390x/lua51-devel_5.1.5-1.1_s390x.deb Size: 90128 MD5sum: 274348233e6f56f3d5c28e611ef39385 SHA1: d179c8e8c5b84445fe6142bd3edf07908f179c7c SHA256: c9920125fc9a7d58ecc27c499e9ad772e0d4037707f8dc51ed3183d0a177faa1 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-1.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1630 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: arm64/lua51-devel_5.1.5-1.1_arm64.deb Size: 373380 MD5sum: 472ace81490ed439d7ddc025b359c0af SHA1: d648d91f3e7342eea42ec266aceac939d2862110 SHA256: 3cb46963397e25bb0576e5d8f56a05850f0acc63814922aefd49584274a57cb2 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-1.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1084 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: armhf/lua51-devel_5.1.5-1.1_armhf.deb Size: 358680 MD5sum: 91b04937fccb48d96ebc707436eeb3a8 SHA1: 5f78f863e08efc31fcd730c52551f42e88fa3192 SHA256: 17231464025078d55997a32887308af1bd70fde0fce8c08db2979e766feabb7a 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-1.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 538 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: ppc64el/lua51-devel_5.1.5-1.1_ppc64el.deb Size: 92948 MD5sum: 0c0b729d004e1b191e71ccad2d120a96 SHA1: 58962136ff347317a7c6df933a347f23ea47f20a SHA256: c315991bf64f588e82737090840da4d96f368779283654437ba5af7809da850e 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-1.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1651 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: amd64/lua51-devel_5.1.5-1.1_amd64.deb Size: 385244 MD5sum: 2fac9c7238ae6f475ae1e0c7cc483f5a SHA1: 446ee18a770f5df227aae5c9bcd4e3af305b0b96 SHA256: 6d582f09d65369c4a228a5801cabd61199b499a07709a8f1090fcce5d27591a2 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-1.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1154 Depends: liblua5-1-5 (= 5.1.5-1.1),lua51 (= 5.1.5-1.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-1.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-1.1) Filename: i386/lua51-devel_5.1.5-1.1_i386.deb Size: 382164 MD5sum: 7e7c6617d3786c4cd522384cf0c8b6dd SHA1: 176581ef635175e7d249ef5948554e7a10ae745b SHA256: 66f14af7f88b1548e135d92f4895fb57156d9cde82386325c33af8dbab0ef919 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-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-1.1_all.deb Size: 71640 MD5sum: 27f2562b46ea54b3be98bca046fa6021 SHA1: 90dfb1dc860da84d8beb896d5c3cc1ab1a7c52d7 SHA256: 50a94fbdce6fed5f38a14f717e9a2441ebd9faa291944de9d56b5a05a8f18a4f 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-3.1_all.deb Size: 29692 MD5sum: 014a561a97773ab03e92048d9e1fbc60 SHA1: 31c71dc6152d391072f83526fc6bc17ef29a4cdf SHA256: 42be7578bad613bf7b21d3e735f0991dbd3ac070f1b31d90a9d00e7512ac0c00 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-3.1_all.deb Size: 22400 MD5sum: 55b1cd5755fb5d1d365a402c4455e612 SHA1: e26e1c1be297f6e4f63037134d2b381d6e153e6e SHA256: e84a98de2c15115b3778fcf80e25f2919f03a9a36b46d2437e28807aced515b2 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-3.1_all.deb Size: 6968 MD5sum: 56cfe6a3b87846b2bd390b77bf7d4b34 SHA1: 0076740ed33c97bb6b9760e2f6b033c0354f5ab1 SHA256: 0fc92e591c10893579b68578c64ac4e74a87ed75a9af2c526a674e2a8367e561 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-3.1_all.deb Size: 27860 MD5sum: cd97eb16b1293ea1908419d6c25725ac SHA1: e0f83658b3f6e410fb75795d63c70af7251bb5ff SHA256: 4b28ea2dbb30569a2db9aea05b723ae3575b52a3926e3418cbbc6f1d64478aa1 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-3.1_all.deb Size: 14096 MD5sum: 23f37691aff59c6a3f2026e7b8da581f SHA1: 264609454032e28acc683574d70040b473d4c3a7 SHA256: 93d191e83beea7bb3a8233c2792ec0be6c1531893c72714bd71d54f247444ed1 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-3.1_all.deb Size: 38492 MD5sum: 94ea38071cfba9c9fb04472cb78ccb36 SHA1: acafb58e34f4e61be2036e79086466e58ed2de5e SHA256: db819b4738a593bf39a67d07c506da9aa9b3582c58be386503a56e2e77c55c8c 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-2.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-2.1_all.deb Size: 38688 MD5sum: 3f3ca5f75c24bb0b6b6f2b003d34f6ec SHA1: bdcdfac7d9ebf10026b3d23515d4bad47eb269d9 SHA256: 5c19056a5930de998c7eb089527fc734878520f00725bf62e66f4c1df6f825ec 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-4.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-4.1_all.deb Size: 295592 MD5sum: 916b240ea6d4231688d53a4027411dc3 SHA1: f61d4320c17f2a09043025d7ca791e186414b039 SHA256: 75d1d2e63074e6dcd8d6e49526671b4db3fb88cfd9b785edda43cfaf9e84f6a5 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-3.1) Filename: all/perl-extutils-pkgconfig_1.160000-3.1_all.deb Size: 10216 MD5sum: b1315e4d06922198969318e395f051fb SHA1: 92e0a36c54cd3a2b450bfa587eb93cb2d1daa990 SHA256: 57d3d66337c6faef7ed03427e520ce94a36087453f9d14f9b62cc6243e379191 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-3.1) Filename: all/perl-file-path_2.180000-3.1_all.deb Size: 30336 MD5sum: e01cba57b3e71fb2feac6fe5c95f16ab SHA1: 3093b4f5835129edb4b3dac68f920ca15ccf4175 SHA256: 6e8363648b7eea3b99852444a07e76e3fc8826e1be739dff579557645fe470e3 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-3.1_all.deb Size: 52944 MD5sum: 65f1f0e3f7f9565e50883f53a623d7e4 SHA1: f8837f9fd7a773cc017984e9249bb6a2301a119f SHA256: d0d188e2aa6bd5a0bacb273dc25a77b76b59103839f1ac26d06fd9299dcca4a6 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-3.1_all.deb Size: 32752 MD5sum: b0d140bf1c4d9ff7e2bcd7373e3ccb79 SHA1: a58774b2ae17298200cd367a8c8fb3c459be468e SHA256: 7391d6f8926de8ff2c01b3af44c36f1ccaf67fb89c96f1cb051943be87993bba 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-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 718 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-2.1_s390x.deb Size: 191796 MD5sum: 34ca41ead5353c8953a400889cac9783 SHA1: f8a439fa1f0d7a280e8e9a7229cbf2f14f7fb29d SHA256: e85a09f796f7ee65d8155f5148ca547614f2df237d0603e8d523e1ea3eba8fc9 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-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-2.1_arm64.deb Size: 187808 MD5sum: ba5e8a142e237dbffd69862ace56357b SHA1: 98f19b0a59d5ba44e8b5a52a9f4653b566880cfc SHA256: 19162db8d487f55dcef13ae9ba1533a4510a02c18c89ce1dcad100102bf38cee 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-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 669 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-2.1_armhf.deb Size: 189716 MD5sum: 9c71415888e689e765e6ce9d4de60964 SHA1: 079ee0442d32f980fdf8d65a746df26fdd9ec02b SHA256: 006bbc315aff06f3e008d1c49bb049c7351cd54aa8ff275f4a58c5407c5f26c3 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-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 793 Depends: perl-base,liblua5-1-5,libc6 Filename: ppc64el/perl-lua-api_0.04-2.1_ppc64el.deb Size: 199292 MD5sum: fdc05a40101883a64f753914850c45e6 SHA1: a4d7f20fb267706f0626d028f7739f05c89f356c SHA256: 0e7e8144552a9de6348b052d04def9fcb8831a2d045331456db6060109354198 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-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 699 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-2.1_amd64.deb Size: 196908 MD5sum: c09d43b022ea8e8390f6d5455774ff33 SHA1: b6905871265f97239325b5e02d12d4a331bf4379 SHA256: 32af89627d1bdd10227e4e982a5ce31ef70984838e7bdd4fe4da74fcf857ad9f 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-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 649 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-2.1_i386.deb Size: 183876 MD5sum: 76c2419886e4c173fb5d26f6cc4842ab SHA1: bacf6cbe0c5b957c055704607dd81064208a45f6 SHA256: ca6b33fa55d831adc458fab928253e167fb2e40dc5bcf787ba523929583fcaa3 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-4.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 657 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-4.1) Filename: all/perl-module-build_0.423400-4.1_all.deb Size: 232692 MD5sum: 3aee24715d08b221f2b027868e61cd19 SHA1: 159e7b370775fc7f2f02fed26b109379152a63f2 SHA256: be1fd9793fe3923f09e19f3490395963f691c287d8faa342a3c90a6d4d6ed160 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-3.1_all.deb Size: 29324 MD5sum: 47824e1ef64e0ef72e4ac39100b5dee4 SHA1: 931a6c0aa2097883b4c01428af74a1ed0f7bb2a5 SHA256: 2bf66eeed2d85fa8829bd9560326482889f829fec7e008f6c1188505f3799088 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-3.1_all.deb Size: 17392 MD5sum: e9b386c28f3af39f15b4d306814ab282 SHA1: f8d0900b020a3d21125253cc3ca148d8b6905d30 SHA256: 34916b2e3887e4ecbd0aff7e4c7bb61d4757c97bc9acd49bcd905475afe7c7cf 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-3.1_all.deb Size: 16932 MD5sum: 36d449fe21c745f66202af45a2795f57 SHA1: 961a20fafdcb34ad9d6469895d110a510686e020 SHA256: 597e59f7518ad27c3b014ca732ec6c23f4c2557bc65b50b1a05e247da3c8763f 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-1.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-1.1_all.deb Size: 8620 MD5sum: c043a6314b41921c0727b3d8e0a32187 SHA1: 099dd9c45775cddc1df7e6c1311227c9f6bbeee2 SHA256: 6fccf97079cf1c852655f315a9a8241b877f6337cc569bb025f215e726e0e03c 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-3.1_all.deb Size: 14948 MD5sum: 95d6ab20dc4526b5d8bc3ab6d59b0f99 SHA1: 6b0bff079338df545ae4efaceae1e8e1b63df07f SHA256: 2abd10390d37acdcc96198f1eb4fe89e2c8d575820b40377475966063e5b387a 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-3.1_all.deb Size: 18020 MD5sum: 7e89d6f5ae4e6b9abcfc034b156acf3d SHA1: 2b9fd7c003fd238d41cee55d5f1a86db15769956 SHA256: d0d3ac395d71b23db73b8379cf7298494d850a746949003ef38d9fec5e863ae0 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-2.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-2.1_all.deb Size: 21896 MD5sum: 5b65de8f93865e2223cbbc539c559afe SHA1: 579388087f54ab1989d9272be09a67ccb7c0af14 SHA256: 11f3b4d18fdc6e042753a0a759a08fc99ffc9de4b5f35a07df3e4911c9bc01bf 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 163 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-3.1_all.deb Size: 55912 MD5sum: 2a0db6b7d35a5f54f26ef5dfe2c59817 SHA1: a0bf3bec50e36b17e43860a38943585906e7496f SHA256: 7e0ff0c4f02d463f3814b68ba1cec5f76b8cfcbd295aa20e2cc2734835d3ac60 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-3.1),libtest-compile-internal-perl (= 3.3.1-3.1) Filename: all/perl-test-compile_3.3.1-3.1_all.deb Size: 19492 MD5sum: 2ba754ff5a6e8ae4dcc713cc0b97bc0e SHA1: 37815d9b296bee47fbceaa08c77fe716f6e9ee14 SHA256: 0ecc3f5db0caca94b809b7bfb4344b7d57bfbde9a97dc1dafd54c8a4e2e2c3f3 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-4.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-4.1_all.deb Size: 86428 MD5sum: d568edda5365d24a2a87f656da0fb17d SHA1: 7f33c4e425561d965edfce4fb17cd9c23eb6270c SHA256: 21dcb1194836e06d34b9e06573cdfe5ff995d19b5b7097132519f62373fc5582 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-3.1) Filename: all/perl-test-differences_0.710.0-3.1_all.deb Size: 18080 MD5sum: 62744e3c86c64ac144436cd2b13ae93d SHA1: dc19f941a9e1bcbcb0df4a1a3965d00da459e3eb SHA256: 6bfd910441cf2ec505acdfef53a63801eb78275f5971d13b1895d9609cd36900 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-3.1) Filename: all/perl-test-exception_0.430000-3.1_all.deb Size: 17812 MD5sum: 2eba8eff089b61d4d835fa865358286a SHA1: 3a5f10566981d8428d2fd8ee8a3da2277496a851 SHA256: 69d1eb020325e2c8130c96e17a82a3ee49f13cebeea4303b8e095ff1d2105b96 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 42 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-3.1_all.deb Size: 22872 MD5sum: 009ce94c69942da9cfa655a4e9b375d8 SHA1: 159cf3e1dd85526db617bc7d2cc9fb05624cb5cc SHA256: fea41d73b2fb37d9fab6e2be0b32f245c625b693140e54ca2f5b81eae9d99cd0 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-3.1_all.deb Size: 13028 MD5sum: 794289d6acb0d9eeafcf1e3c0719828f SHA1: 394a89d89150584cb6014683d8c80ce1e13ec333 SHA256: 52af90516e9153dc635b2fcfca35ec60ea436dcf207620663ca44a751189ac73 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-3.1_all.deb Size: 10664 MD5sum: 1c995bbe0c633f9405101ad58ff8ae1c SHA1: b3ef12dbd2bb0a967d55b40c5fe2b0c8743805d5 SHA256: a3eeb9ee5fff954584cd7969c58a626cc007ec5877d59f12c4334a24ac36f027 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-3.1_all.deb Size: 14520 MD5sum: b6690307a2f9752e7fccf019bd2ac380 SHA1: c1a4556ae220f273e201943e9a60bac5dfce268a SHA256: e63402e17db79d7aef76910d36e1c45a27403649665ea03651aa42ebd4e36bbe 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-3.1_all.deb Size: 32488 MD5sum: d1d82360f9a3b1c1bef6e2c1d13d3058 SHA1: 42ddac4217d5e4bb4add252672961499dbccf67b SHA256: 36476efb23b118ad169b6cfb8f9ab91523439d4424d1cee67207b59ca2b84326 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-3.1_all.deb Size: 23668 MD5sum: 49c9e6f82787e57fd99b4e32054d02d7 SHA1: 56ed4c6284e2e9617d56915193a584ff3564782c SHA256: f7bdc06506ac4ffa1ac9bdcdbf44432762c7c49613a71e341629bcc7912c8d55 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-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-3.1_all.deb Size: 8620 MD5sum: d294be07608b4ac5a702c180bb636597 SHA1: b0fe298f82ac7ac53fb4f0a4e57d8daf98bb6329 SHA256: cde064315b87f83c3d48dc2b1ede04eb62ec0b7e0adb2bd2003a80c0848e4e3d 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.