Package: deb-perl-macros Version: 0.1-3.1 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-3.1_all.deb Size: 2892 MD5sum: 73ce3cbd72559df60b686919ed34e210 SHA1: 52eab2acf5697b6ad84250b986474099d31dca86 SHA256: dffccc0840b97109cf7f8e8bc10695d0a42346f4c86ee5f109ec5a60f033f130 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.2 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.2_all.deb Size: 54892 MD5sum: 5bacd4921531518a583e3ec850767e24 SHA1: 4e086529275d46947d354dc876df44a277ef9fe9 SHA256: 97655dff59b4c83b297f9c7174e04584cb9ab05ef682ee8fc8b10b8ce84c32a8 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.2 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-3.2),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.2_all.deb Size: 8624 MD5sum: b9a14e98fbd5899ffdbaa291ab6be1e2 SHA1: 04b58dc0df7fc9b00b69beac380e06e48e8224fb SHA256: 29b4c74511392d219558e13e08a69996122cd8f7e45692ead35de94bc8ebc722 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.8-4.1 Architecture: all Maintainer: debbuild developers Installed-Size: 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-4.1_all.deb Size: 25620 MD5sum: f5f59613084b8f16f30faf2121d9e4e9 SHA1: 4cfed4151f457defca04bfe6ffebec918b4ea30b SHA256: f741fddc3ebe5c1eeac5e2bca6d1d42754fedc609fe6206f841e419e04748ecf Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 327 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: s390x/liblua5-1-5_5.1.5-2.1_s390x.deb Size: 74612 MD5sum: 6e684bce91cc9c49bd074b84a33494d2 SHA1: 1b498fd57e773f3e60d16e0a38209be2a6475d04 SHA256: 2cec77bf6dfc6a7472f6986d6786d3d2e483259a7dc5af1ca3ca170894f8c6b0 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 839 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: arm64/liblua5-1-5_5.1.5-2.1_arm64.deb Size: 295396 MD5sum: 0bec7b2022cf6eeafd3449b598ae33b5 SHA1: 91abda98521f4ce3680dc498c2329d1741d38925 SHA256: d9079a390cfa9dafbc74be39a196776a67dd98a21fbb2f7971f037912f2534e8 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 760 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: armhf/liblua5-1-5_5.1.5-2.1_armhf.deb Size: 284580 MD5sum: 98e93aec7875a0e561bb2502261e2f77 SHA1: aba628fa147ba30ff65330931f0fa3e1d88ed12f SHA256: f1d29998de561002c72e4e04b61e96977f13d3e099e00a5886d907d86d5fade3 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 369 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: ppc64el/liblua5-1-5_5.1.5-2.1_ppc64el.deb Size: 76912 MD5sum: aeffbc1b95777e59e1a917aa5f38fba5 SHA1: f6363deba01f6a8486658cca3b4abd462d480d4d SHA256: 58ed6f1dd6a3dab50c7b58f24f3f19a7772457bc9f9bbf1f4d023d54b3e68f2a Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 833 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: amd64/liblua5-1-5_5.1.5-2.1_amd64.deb Size: 309824 MD5sum: 686c91df2624d6e8baa10fdc1683e4cf SHA1: db51ce1fa08a75c06d7a908de4a86945562f6e63 SHA256: 5bf20f871b6717129579eb9bf75f75c66e6f7c1e3f6628f4c149decf23d27a18 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: liblua5-1-5 Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 785 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.1) Provides: lua51-libs (= 5.1.5-2.1),liblua5-1 (= 5.1.5-2.1) Filename: i386/liblua5-1-5_5.1.5-2.1_i386.deb Size: 306740 MD5sum: 1eeb736c2ed77fc603427fbf443f6c3d SHA1: ed45111806762caf860e46276354050cf30d19aa SHA256: 56b2681a601d9eab3dcdcedb36b69fd3149d6c7474af662b88c3cda35729ce2e Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-3.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 1 Depends: pkg-config Filename: all/lua-macros_20210827-3.1_all.deb Size: 1724 MD5sum: 3ed81766d9a702c998ed618be7ab1e09 SHA1: e9debd2fc696fd1f19f89527cb1d88f4051974e0 SHA256: 93b74ec8653fd87e12e2fbda15575363165c2b8c4c6b40301c83c503f6482f90 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 544 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-2.1_s390x.deb Size: 89104 MD5sum: 1b77fc1d12a4dc2ba01f5f3c26134879 SHA1: fae92a25829c7ac0d9c387b3976803c1ee3c202c SHA256: bcfa80f5e8bb50ed305a70c45230d085f2859510e253065e117d02eeebfadc1d Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1465 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-2.1_arm64.deb Size: 359372 MD5sum: a535d73b818fbb6c4b4eb05046bc8374 SHA1: 06ae1d4cc9ce84e91e5a74f269ad433a1c26e1c9 SHA256: 52e113743ffcc5539b6955eac0cbc5491f8871722133b335b121af17a3ff5187 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1310 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-2.1_armhf.deb Size: 347800 MD5sum: ae20a6cdc98b6e02fe6241da2b0b3601 SHA1: 44306a6646ad2fb670a847f86ffdd6a672b48d75 SHA256: 8730601c9b7463e3d9cb9f682b5d04ecc924ddd30cd71d0503d21551371ad958 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 585 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-2.1_ppc64el.deb Size: 92036 MD5sum: 8d0ad0a702516055e6775246bf3f4dcc SHA1: 7745b73419aeb8853e44e2b068281cb568eda1f1 SHA256: 2f67e86e8bebd3b5ae228dd395ce4a8ec479bfb0e5e36472fef340fe532c41bf Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1444 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-2.1_amd64.deb Size: 379136 MD5sum: 3c9138fdfb0ed4f0e56514a5cc3e1e11 SHA1: 7744f8e8584a40f0d6b423b6ddeefc4ced00070a SHA256: ea955d3d4168ee763642b34d2e4cb3cc803f4f157c7e1496d3688b7aa3574a41 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51 Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1363 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.1),lua-api (= 5.1) Filename: i386/lua51_5.1.5-2.1_i386.deb Size: 375168 MD5sum: 7866c485f3f5b1a68c6380817b223c29 SHA1: 0973e9ec3bb16c394c8d67cd0dadff22ef0f3ccf SHA256: 5c46d218f9ec58053a716737dec43edbbeffe185505abe2c5656857b94892ce8 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-2.1 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 516 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: s390x/lua51-devel_5.1.5-2.1_s390x.deb Size: 90080 MD5sum: 6ad04f3f91623d495bd75fdac8e389a4 SHA1: 4ac3b9320f213c32280bfa45956abdc8bdcadb79 SHA256: 1c7126c0e5bab2a58c788ba9043c6a8361be4c09ec281f2fc7ebc08ccdfd8e0a Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1630 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: arm64/lua51-devel_5.1.5-2.1_arm64.deb Size: 373224 MD5sum: 437d1025b33f209d30a1af1a05bba660 SHA1: 5fdecd5bb816baeb3d1bc4896d213367133931d3 SHA256: e206988b6ec4cb5e03aed7693ee1141a638abf9c0c69b03318f899b8fb00683c Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1084 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: armhf/lua51-devel_5.1.5-2.1_armhf.deb Size: 358768 MD5sum: 9ff27be152b72bd220e8c2c35f4d0d93 SHA1: b9a494b535b806873e4cf430cedf09d2ed15e9b1 SHA256: 0108c319b4d8d9da0ec5bc8632bfee26663fea9428aec435f24b9b2afb8fffb9 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 538 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: ppc64el/lua51-devel_5.1.5-2.1_ppc64el.deb Size: 92920 MD5sum: ef9977437ef3e4c6b6603d2d7e35b375 SHA1: d3cad99d97087dc8a8a2506500f40af13a27f382 SHA256: 4e0a1c5ede1ba54799f915d283907c7354142309348d122f4a58ab43f5a05fba Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1651 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: amd64/lua51-devel_5.1.5-2.1_amd64.deb Size: 385252 MD5sum: 19f54e6a2b4a01d06f8aa6e06b3c8710 SHA1: f47d76b6e1391ac2cd1f97de949d06cc376bf1dd SHA256: 26984f91ec07b85f24fe8b5fcbbf7d8d696b6e1d3728a572c4006c2dde9b18c1 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-devel Version: 5.1.5-2.1 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1154 Depends: liblua5-1-5 (= 5.1.5-2.1),lua51 (= 5.1.5-2.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.1) Filename: i386/lua51-devel_5.1.5-2.1_i386.deb Size: 382076 MD5sum: cf5d6adb3d79ddcb6283d31fa4abfacd SHA1: 88e608fe050f85aa277482bf4a1834b5b1d2be64 SHA256: e17654ab7fdd66e82a4d4b64ee994bc0c7ba7b76dd13eb1d9be10afe2c1bf998 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-2.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-2.1_all.deb Size: 71632 MD5sum: bd4db10e8875d1ea76a36cf07cefca2b SHA1: 0eee24f0ae583bd82641845874b65c8962d2dad2 SHA256: 1a23ffe273b6eb848ed11983692510f9badd123a0e53332dd3071f69da02c91a 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-4.1_all.deb Size: 29680 MD5sum: 748e8cc39ad30d36552d6f1be6c1edca SHA1: 7f81d93b4ff0b75d029f564b056780acf2d2b9a9 SHA256: 6f096b3c8092fa6eec2a138c1572a72006ae8744224c79958269dd4c2875261f 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-4.1_all.deb Size: 22392 MD5sum: aef0e9cc82665eeffe578a0affd0873d SHA1: 90f299cb4262f5c5f1ffc9459652c36a5b10f0fa SHA256: 0a95318f2c8ef7d96724821ffad111119effd7961c3d06862f64f50a90a94bf8 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-4.1_all.deb Size: 6972 MD5sum: d8ae2e34e230241934f98093e4f5dd82 SHA1: 0ecc72235084a3c74539c137f35b454ebaf46314 SHA256: bb3e54512ed2a1a12d07f5e1122973e18a8696cf53acd0d3998dcb1194357220 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-4.1_all.deb Size: 27868 MD5sum: 3c2b671bc00504b89371baeb367a8315 SHA1: ea1e482bf9ad12423f0d2c8fe4d0f9c7fbc2963d SHA256: 2a5480dad435e6ffa2ba2d2cc51a6faa0251aff6c358efdba3264992ae485489 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-4.1_all.deb Size: 14096 MD5sum: 5019c6562ab87cfc873e3aee7bd337d7 SHA1: ec61ce06ba24206fd11fb4a43d055be6bad94475 SHA256: e856ed06e8857d18f915336fcf23ec938f6608589918dde0a77708990595fdce 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-4.3_all.deb Size: 38484 MD5sum: 675146125e1952d5bb996f6de78dbc18 SHA1: 3507295ccfe533d72848f3a5857269a9a96b396a SHA256: 4a92e4332d5a3b2b500ca3fbc846ec97cf458ce43765513a93a695bc602ffa16 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-3.3_all.deb Size: 38680 MD5sum: 53b68816b56b4fc0c0f7a8aef43b25f3 SHA1: 9368f942857128d814177d98c414e7283d2e039d SHA256: 0875d0aafd7c6c83442a2f0ab05e79e7412b5c034fa4e217cdf62f2a34046141 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-5.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-5.1_all.deb Size: 295552 MD5sum: 138b8b4471b3a4a56a79a06199df9595 SHA1: f7e7496a524705e75f72c5eb0955b9f473c74f78 SHA256: c6c7b2f0d4eb242466c3814fe2236ede4ff94b77d350e6debc9e7e34af4056db 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-4.1) Filename: all/perl-extutils-pkgconfig_1.160000-4.1_all.deb Size: 10212 MD5sum: e190fd537230a506fbb0ade83795a544 SHA1: 1fedaad606f92b1cfa8f412edbebb7bf9f0f9b00 SHA256: 404b2bfeca5e3e933e0bc24f5d1a32898b260dfaaacd29fc74772895134b673c 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-4.1) Filename: all/perl-file-path_2.180000-4.1_all.deb Size: 30336 MD5sum: 73d5d887e5e9d28646c1c7d1d466db6c SHA1: 40822e69554e546c3c5c7534a1814f8e958de320 SHA256: a1fbabf8622ac2b3c23046183a5c0e70d276a88c9eb7b370a057e1bd9ad7aa3c 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-4.1_all.deb Size: 52920 MD5sum: 344733058fad767127080af8ab599c23 SHA1: a890b5da7dfea03c57b29db47bc3e9e4ed3f5f06 SHA256: 58e1ef19edd4d09cce8eec4ff7e369ed61aa56968f9de1416381fbe8c25fd324 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-4.1_all.deb Size: 32764 MD5sum: 4bc72ae7851e9fe3353f39bfe99af221 SHA1: b87475c62a9580043ce68066971fc67b8e8bc19e SHA256: da17df4f0827c6746ddd317d0e1b9f3da962c342e871b0eea69d6a072df54985 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-3.19 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 718 Depends: perl-base,liblua5-1-5,libc6 Filename: s390x/perl-lua-api_0.04-3.19_s390x.deb Size: 192556 MD5sum: a9f6a66ef746068a41c418ce7803155c SHA1: bd6ef6d46d8436beca934f15cdd17df062771b95 SHA256: 6fca5bdba27de2a77e3be14ad2ecec2acfd1d2a471b6c8e3a341ec3d53bf1876 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.19 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-3.19_arm64.deb Size: 187884 MD5sum: 1a4a68def2f91bc85bccdcfaec4b2427 SHA1: 662f5023934e76063eb5900c391dd8c17a4d2013 SHA256: d3939a90f67027cb19e78c354714ec7b406bf42c6168d0f051bfcdac05250589 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.19 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 669 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-3.19_armhf.deb Size: 190008 MD5sum: 1996084dead28577bc445406d28c65a6 SHA1: 4ae36a41cedc0c2e0e1f46380ba01798fdbda42e SHA256: aa3e8f82c627c1fa842f92374ed5d12c36d90e1d0a4d980a8366aebc9806c234 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.19 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 793 Depends: perl-base,liblua5-1-5,libc6 Filename: ppc64el/perl-lua-api_0.04-3.19_ppc64el.deb Size: 199028 MD5sum: 701eed4aa47fe24fbdc1200f82308daf SHA1: c90469e366fe0b2cf3c790a5ba75ed7cb0720be5 SHA256: 358d803c7d2a3d1f1bd560e82605fe086374b341c9c2dd2d8d9a6a777d9eef78 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.19 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 699 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-3.19_amd64.deb Size: 196688 MD5sum: 4fa199ed28882abbe7123cf04fcbc82b SHA1: 0c99d42f5ff7a957c9c37c78d7bfbfff4d8bbef1 SHA256: 615581857b5caea5c508e6dc6bf2884e6c68594a61dd3032d4e6ef5eb052a881 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-lua-api Version: 0.04-3.19 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 649 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-3.19_i386.deb Size: 183616 MD5sum: 459847e154c4aa3c3e1eed9f10ed0ba3 SHA1: 99d184a16b6b1d4bfea41746f9b5de31caeec12d SHA256: 3bfb954105d7596db8ecab46f690238f616368f0158fbb11163fbbb4149fa4f8 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-5.4 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-5.4) Filename: all/perl-module-build_0.423400-5.4_all.deb Size: 232672 MD5sum: a1b971f7cf169fd4a3a4d2ad7ebf8f4f SHA1: 5cd84b1cfee824b63888e45a5fdf2c95f786cd1f SHA256: 84489048c088aa2a8c4320e39c914fad11eaa13455127228e2d57888f6d5dea0 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-4.1_all.deb Size: 29316 MD5sum: d0620eb70924396360c3bf89c393d073 SHA1: d7eb6f7430e1a137a2511f120f8c5f6485f07c27 SHA256: 0962dd80902ae2163a9504c66d067c81c66cfbd7dba9f6bc0c015ab8ccd36c52 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-4.5_all.deb Size: 17396 MD5sum: c780eca87e8035d6ecc1ec6333c85152 SHA1: 6a1404b5face4b64950e5fe41c56d972d6ece6ee SHA256: 50fbc48035de612b7a874e126da554a0e5e42108f3a4840ef50c95a93f78fbbd 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-4.1_all.deb Size: 16928 MD5sum: f06529a8d2f1201d50e729ce448fea65 SHA1: 000a6733cbc77bc9a28a617b0605474f2f78c654 SHA256: 4b2233659cf9fe4a404deffc22d82e9be29558f38aa41049b2d90b1100c7a291 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-2.1_all.deb Size: 8616 MD5sum: 43fdf08581c8e3cee6cc636a0f8c1321 SHA1: cab7a45f6331fa6ad206d18b79fba4bc7c48830f SHA256: fa84b7826a023e7869740b239b408398aa4654460c4697a0c629925e7da2fb8c 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-4.1_all.deb Size: 14948 MD5sum: ae4366b470194b8f2272fdb879545754 SHA1: e3e02f9eb8d41bde730c81ef74490fa6e633cec3 SHA256: c87f9059084641210a7f512a40cced2e221fd10a186411e006ee67367b177181 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-4.1_all.deb Size: 18032 MD5sum: ff67a9402a3de7147bdebb23ca7352c7 SHA1: 8b4b23aee480cd0f87d050c8d156690d7c978e00 SHA256: d75a1e93ee036fa23f3e3577b11db82365cf4c36d08ccf92e2cd5f9bef4be709 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-3.6_all.deb Size: 21900 MD5sum: ab851979efbcc117915573c4c8eb62f6 SHA1: 78032053af570759d7a59e496a9f778370e43585 SHA256: b59fc03c58e649d59ab496148b8f23a63332fc330b864fc62604706d153bea11 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.10 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-4.10_all.deb Size: 55916 MD5sum: 60c4cd0fdccb33a0a3c7c2407ac38f41 SHA1: b0efcda4e6fe006eaddef53e7130751f9064d9e9 SHA256: b3738c2fff2ce5fc454524485ea67969bf795d0d300c0352719784c196d24a25 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-4.4),libtest-compile-internal-perl (= 3.3.1-4.4) Filename: all/perl-test-compile_3.3.1-4.4_all.deb Size: 19504 MD5sum: a593194a44bd7fd78e4b81ee0a6dd3a1 SHA1: 4c4da42783e19117503de4f99d57c8e231fc1400 SHA256: fef0b1f98a457fc93c95b90b7b57f0b03eb3469aa5247b75bf52204bddaf6e2d 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-5.2_all.deb Size: 86432 MD5sum: 5f47cb551cc6e09c345d7c2119d39a06 SHA1: c4277614b72d3b91b4094204b43760113fa8a397 SHA256: affad76b1b00640afa7f44f183d303a28a3f4b640aa5c6104a0c36dc5d29db8a 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-4.3) Filename: all/perl-test-differences_0.710.0-4.3_all.deb Size: 18080 MD5sum: 12c41d042b62736103e96a07a808e287 SHA1: b8ecac51ef0dd64c8765415a46fbe6d6218f0cda SHA256: a5c06d2cf74b0eb68f5a1d6f6111e56c1d37967217c58f5e2b94d3ab48030372 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-4.7) Filename: all/perl-test-exception_0.430000-4.7_all.deb Size: 17808 MD5sum: 8d47230a4656a3896c0bfaa7e33914e5 SHA1: a47ffcc9279041e1e1c6afcd22d5033773971749 SHA256: 7e21b9ce7ed32ca89795f1b32b50b0851c1939d3fd3b91a5ed2d406131991c10 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.12 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-4.12_all.deb Size: 22868 MD5sum: 70a3484d1efdda61ef8caf2f3d3484e2 SHA1: 3cf73229e79b88d0a67a7e9c813d619c6b162964 SHA256: 3d689c8c0ab08494dff9df2358b48084fd62524bc77be36820d0e7aadef41462 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-4.1_all.deb Size: 13024 MD5sum: b2273765470264380b073b28ea7411cb SHA1: 5befe1e7e6c971fbbd92aeb4575d88f8197819cd SHA256: 1aa5df79e27a59e63bc3fa1254090a930c51e2e3134a3018963561f62026701a 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-4.2_all.deb Size: 10664 MD5sum: d21424c1c37530b2533865cf44b2d925 SHA1: e3f9137c8a8c20f593fbf7688608ae9e439250ea SHA256: afe605d747bf826eb04c07b22c50fdea866f603d4ab4158ab3c1c5fa42cc1bf1 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-4.7_all.deb Size: 14524 MD5sum: 071c1ef6df61788f6156540025294164 SHA1: 8aff1319d0681e6620fc06ea7d4517b9668283d7 SHA256: df1d5378103023c1a58d67534afcc9bf2d3008f4ebde3535e6ade00134b184de 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-4.1_all.deb Size: 32480 MD5sum: 5f35262d4dcf1ab14f1674ad375f4675 SHA1: 47279e10dd169dd91e4759264d5a6fef83e32693 SHA256: f8d22ab27f60a804d0fcec88c51c2d3dce26f1233e239ff443db56eea6464135 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-4.1_all.deb Size: 23672 MD5sum: 0e24bce560e434b5eeeb01b8bad66661 SHA1: 7020bdf1d9e33718344787f8b7d7a8b1bd404404 SHA256: b76b02ed5e8489c1116407f1e2b53538ff7a632ed7dff5039f1a03bc82a31aa6 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-4.1_all.deb Size: 8624 MD5sum: e151a3853a9299c53c29de37c5e5a2cf SHA1: 45c2fbefb4af2b5e59390ebdf8d45e4154122ba9 SHA256: 86993d5d17cc46a15a0ab5f31a4583a44a867f85c3388c21c276e4c58110cd81 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.