Package: deb-perl-macros Version: 0.1-2.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-2.2_all.deb Size: 2700 MD5sum: 0ccb2314d5e14e4fb2ec8e793b5f01db SHA1: 5173c9d85aeb814fd43b3b01d520795861a1e8ca SHA256: 526a9ccd08eeda63449d724a7a197500b3ececeb17c8e83a9879da7877bc279b 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: 23.12.0-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 209 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_23.12.0-2.1_all.deb Size: 54792 MD5sum: 4c492b7d9bef4d6a37a54bf029a08ea0 SHA1: 064d066c4693372cfa9b72b2f138c394f34e62ed SHA256: 81a7b3adc2bfe41b44e5680b9849646095cb9e90d53e6ddee9bcabc4c37342f3 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: 23.12.0-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 23.12.0-2.1),liblua-api-perl Filename: all/debbuild-lua-support_23.12.0-2.1_all.deb Size: 8416 MD5sum: dea361c2fe95c1d8e894091cbf0384e0 SHA1: 4025a7fac111117cd30413658f7db0c74c58212f SHA256: 7a739b3cbfb8a94527abd6732d28b05127492346b33db9fa791567a0f3eb1943 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.7-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 126 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.7-2.1_all.deb Size: 25504 MD5sum: 8c36567d6801003a33730921b476b28a SHA1: 4f913c817bc7b369a7836159098406bcd50cf0a2 SHA256: 8c92a4d03b138941879a7c1f807c61cc2a53b42082ea1e5dd2116eeea564c112 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-45.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 401 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: ppc64el/liblua5-1-5_5.1.5-45.3_ppc64el.deb Size: 76844 MD5sum: 6a36ebf1d14fe0ab326729025f682fd0 SHA1: 6e49499318a0c913b93e626666b8d886006c7893 SHA256: 9ebf631a6d536dabef3ac76570456536c6eab109f502089b2bc46cd5b1268b39 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-45.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 359 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: s390x/liblua5-1-5_5.1.5-45.3_s390x.deb Size: 74768 MD5sum: ac84595787225f2a17e48e32002997a0 SHA1: 37eb0987d26546fae23bf39d06094501eb66afa9 SHA256: d472d960b30646ac50b364a0944190051e52dba2c819785bae804eeaefcbbb90 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-45.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 749 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: armhf/liblua5-1-5_5.1.5-45.3_armhf.deb Size: 281904 MD5sum: c2768a46ef5229abdfc2ed652b6031bb SHA1: c94472377687ecca3197197f3086a7951f7395c9 SHA256: 7bcba3fa954288d2da256e7377d1f6f6db33b919a54a17d5457a2f4ac182ce80 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-45.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 862 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: arm64/liblua5-1-5_5.1.5-45.3_arm64.deb Size: 294236 MD5sum: 2899195674d35b0fec40c04c544c5819 SHA1: 4ff8ebd5a16925472310825ddb20554d154f073c SHA256: 9a477a7595da8be01b77a1a6ff5822cb9d08e0133b127f1b5aedfa77ce562cd5 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-45.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: amd64/liblua5-1-5_5.1.5-45.3_amd64.deb Size: 307552 MD5sum: 315e0ac63d243c4316b191c2d0089fb9 SHA1: 0e5bb55e00fdf33e9a3cfe37fe7630cbd206899d SHA256: 12330db7c728f05de9b42c12d1e41f93512e5e161f6aebd98aed111bba6bcaed 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-45.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 804 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.3) Provides: lua51-libs (= 5.1.5-45.3),liblua5-1 (= 5.1.5-45.3) Filename: i386/liblua5-1-5_5.1.5-45.3_i386.deb Size: 305560 MD5sum: 1c5cce54808d731879b8087b8cd4f1a6 SHA1: 16f3b77e2efda55f8a8d93cba5aa0009a52d0afc SHA256: 57c19783df60291bf1b559e8ecfba9c043ec8dd95747dd9ddaab6a6390c0ef38 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-28.1 Architecture: all Installed-Size: 25 Filename: all/lua-macros_20210827-28.1_all.deb Size: 1528 MD5sum: bd470469ef62c43f043c7aed57e96866 SHA1: fd3ee14c3c4b7c38dd2a5d9ee1f26e174fb37f90 SHA256: 80f9f56a2fa44e684c2822d879333fcba1573099e12c670d1cc7992fb4b70cfb 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-45.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 645 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-45.3_ppc64el.deb Size: 92664 MD5sum: 6a012c7c67d6182c547ce932c8102beb SHA1: 8b7e3c0ff34486caa0ffec67eaac6de63e280694 SHA256: 730aa7c8f807d0cf308201577932b1cce5abe12f6f967a24c74784630107c236 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-45.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 604 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-45.3_s390x.deb Size: 89840 MD5sum: 3d42c9353bd26e1814c01673f617f755 SHA1: 72c3952a3f2e3b284ff0431d9bfd9bcdcd4eb9d2 SHA256: 046e1c02edbfcf4f37edb68a98944cd88178a22e4f32e36ec7299b71e1629bae 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-45.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1314 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-45.3_armhf.deb Size: 345028 MD5sum: 01e7b932be02dced12d65d31da237214 SHA1: 8c709ce47eed42aeae9586fb97a154429b077d73 SHA256: fa1ace8dd1de8041385f61c69fc85152d306a280913c7a993c4a0482ade4ad70 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-45.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1510 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-45.3_arm64.deb Size: 360520 MD5sum: 0ead4fc6610d994d7a3a62d3395d1e9b SHA1: 74201946bc4145287ba57db946515a509c146fd2 SHA256: 7c395567ba12a000e0f2a05969f4fe5f2c54e89c40f84ea55c4797e9b3e83b67 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-45.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1489 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-45.3_amd64.deb Size: 376812 MD5sum: 93ed079770f462eb3c1df3afc6277bf8 SHA1: 27f450d9444633ce8320872530906a26d0037109 SHA256: 81e7052793caea9c32eb00e6af35acd8b5c0bdc578fccdf5c8c3272c36dd7357 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-45.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1413 Depends: dpkg Provides: lua (= 5.1.5-45.3),lua-api (= 5.1) Filename: i386/lua51_5.1.5-45.3_i386.deb Size: 374480 MD5sum: 6587db3fa6b87e5d34d5f3416fa41c6e SHA1: 2365bfe9ba9b720b209cfcdd570b46f4a45ec244 SHA256: d0fca1b96412d880ccb1188e278143591680fea49c2a4c2e5b38729c0c63da6c 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-45.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 582 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: ppc64el/lua51-devel_5.1.5-45.3_ppc64el.deb Size: 93004 MD5sum: cb0858f62983678ca204bb2e5a31115e SHA1: 66cd6ee5614f8ad6d98107745d922e84ce837018 SHA256: 4f2bc06876d5421f13e0670b154cf93e685d4c158bb90a486bc36cee4eade8c1 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-45.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 561 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: s390x/lua51-devel_5.1.5-45.3_s390x.deb Size: 90272 MD5sum: 6880f38588f824abaa60ed0cb60587fd SHA1: 76cbc4dce00d2b68a287ee7c213d09bafabafee1 SHA256: a4fd82b2bf49e0ebb18d9a3dba0fdacf88607df5cdc2b9bf1792439b0d775cb4 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-45.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1109 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: armhf/lua51-devel_5.1.5-45.3_armhf.deb Size: 356188 MD5sum: 3cb194d7b476692845a359d8e4e57866 SHA1: ea654d84d936cc57f86f739fef122842846f8a0a SHA256: d62048a1a285f0ee3b4156c5b48bd46578ea164b75e74f5f8efc7c563d9c766e 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-45.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1662 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: arm64/lua51-devel_5.1.5-45.3_arm64.deb Size: 372420 MD5sum: 7d49779b6ae28c478d0dc82488b5301e SHA1: 2ade4c0c538db12d031d1e506d916d290c459911 SHA256: 53ddb568600f24d57c9451980b64f01d9d2a2f6e09c55321b0e53ef55dbcf7f2 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-45.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1685 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: amd64/lua51-devel_5.1.5-45.3_amd64.deb Size: 383424 MD5sum: fad2326bfddc4c97e3fccaa28d1b6bb7 SHA1: fa7ae7823d80d97df79ddfb8ba75fcb5ef7367a3 SHA256: 830fbe3f35f76f7e7751aa7e4bbabd50865aeb1f0fcb73df7511c266b183dd95 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-45.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1189 Depends: liblua5-1-5 (= 5.1.5-45.3),lua51 (= 5.1.5-45.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.3) Filename: i386/lua51-devel_5.1.5-45.3_i386.deb Size: 381892 MD5sum: c8b0d698c4bd016caf9ac60f4f2d35f9 SHA1: fb8a8e7ebfbd47bad237cb49a37a222673df0be9 SHA256: 7e431094a393dd9552366e9da5713c5ce554328968c604ca2a1d2e4bd5976867 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-45.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-45.3_all.deb Size: 71680 MD5sum: 5008eae2505aa1f3efc5da515cdfc1ad SHA1: 8f0d5bf491af52845882634718dd9da5b6d63c9a SHA256: 6f9da9d7dac734b17addb0270afc4dfc303c68d9a28d3240508cfbaff5c19fa1 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-3.2_all.deb Size: 30008 MD5sum: 1d98744c6354d8873310a6b3552b08c9 SHA1: 820dde81b6ed4b2b15880923e7a76e83b9694d55 SHA256: 413f66114e53fab2df99bd258d91e5965d0757ec8999abea6c78ef7104e5c7d5 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-3.3_all.deb Size: 22672 MD5sum: f51591cb7402526f756fbb828fc43dc1 SHA1: 80b6d4c36911dfd57f70244dc9c353b221b2e1d9 SHA256: 35cb52ff6221b290f61f913897aeca0d0e5794ac5cd28750f4da2e2fa19aae15 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-3.2_all.deb Size: 7232 MD5sum: e637910ea0b3dd2c215284152eccd013 SHA1: 205f2b4d64580e4babd4a819668715e4a3862963 SHA256: 125d66a8a2e7d47438263d790fc35750b051656f2f66d06a32eb6d152233f92f 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-3.2_all.deb Size: 28392 MD5sum: ae3efb63dac65e63ca0203480b3ca423 SHA1: 6bfad8fb663a722dfe5ecc8c068ba0216d12ea13 SHA256: 27deaeeb60ac8c2ad9ca120fda0f3f6f6efec905f3ab65a6759421834c24feb0 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-3.2_all.deb Size: 14368 MD5sum: f24b5ef7dd9083a0e9b37f73b95da02d SHA1: 7dad95fccc4d943e92ddd032eb8e5cda9a3fe0fd SHA256: f74ba0d7411106f8445b3dd5a4d1ee54891fddd5fe7154940ed2e4307f05649c 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-3.4_all.deb Size: 39068 MD5sum: 1029262d9cf88b1e533e755ed6b0599f SHA1: 21d8cff1fb6b7acab315ba3e7f4c8006aeb91807 SHA256: 12a5b10b98b02e3efd1d4f18e7fa36524bac0e850599bb1c54baea2821f73908 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-2.7_all.deb Size: 39252 MD5sum: 027944a3cc2d0d52c76d6ce4952cc670 SHA1: ecd733ee76feb8bf4ba0c5e0ceab3364fa6d8712 SHA256: 45660f036e58db733dfab7a5a00eab00d2cd5ee996815a339d68dc161b2b55c3 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-4.3_all.deb Size: 304536 MD5sum: 9044c120e754bdc3fe02c39fb58075cb SHA1: db94958e451cc7bd1da292d2a06ae3aa2faf6eb6 SHA256: 5926e2c06c70f9dcd12b78e8dfb38a952422c097dc19e0e0f1e6ea11c11a3198 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-3.2) Filename: all/perl-extutils-pkgconfig_1.160000-3.2_all.deb Size: 10552 MD5sum: 6cf6cea4d62b09308a52e55a6aab6d74 SHA1: c7e1e340e030f0dcf2659fa06a93b6ecf456ea71 SHA256: a5283e0a7d5818b99e6c9516dcb1b5f288e4da44f85d1a9099f5757b3a775ac3 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-3.2) Filename: all/perl-file-path_2.180000-3.2_all.deb Size: 30668 MD5sum: c9ecc0e4056d44671707909af1ab6256 SHA1: 4ab56a086fe79f8c480e284b4dd3987b1036eec5 SHA256: 227346a6472155d433194d131699fa294defa58872cbd5cb7fdbf348aafb8b5d 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-3.2_all.deb Size: 53276 MD5sum: 818bb46cc2dff128364737a441c73752 SHA1: d155cbbd20de22aa19f4c48504a0f922046e6874 SHA256: 97655bde7b8d6cb709a3853dcff98a0210fa9821140ebbbb5e54de2ea559ab03 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-3.3_all.deb Size: 33144 MD5sum: 6973073f6db16db23b920eb307a89e48 SHA1: 4bc44dbed164a064b8eaadda3cfd03255fc7cc83 SHA256: 6de976edeb3fe4f076c465c95e3cf92b7fe251b29c8e5cbb99a61b106c3c8316 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.30 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 790 Depends: perl-base,liblua5-1-5 Filename: ppc64el/perl-lua-api_0.04-2.30_ppc64el.deb Size: 177156 MD5sum: 1f36e6f01a317afdc7bfcf3451c8eea5 SHA1: ab01a76237de95b7ae910ba5a8c8518634c2830a SHA256: 49f66057e29d4c2730c82af7e51b80e68ad18c51cc63fdb60294a03a4cc18d5f 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.30 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5 Filename: s390x/perl-lua-api_0.04-2.30_s390x.deb Size: 167840 MD5sum: b9d6d1b787b5d018dae2c0f237de25d4 SHA1: 84307e9ead1ec866a293dcb89c61ccbf44506f92 SHA256: c02ad81ea6821ac486e639e4bbb1b18c4c28af223dfc6be900663c5b24cc5fc1 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.30 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5 Filename: armhf/perl-lua-api_0.04-2.30_armhf.deb Size: 169920 MD5sum: 1bb77ba88978147ac8b29e52d24d4f48 SHA1: 7ab1ad1d77cdb2eea060f3d7c4da6858312966df SHA256: 560f54e37a76e987395e9f6100842ea5b89bdb2745c89e89715ed86abd05da92 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.30 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5 Filename: arm64/perl-lua-api_0.04-2.30_arm64.deb Size: 166836 MD5sum: 6dcdbdb61d3732304be03c2cd43892dd SHA1: 32bdd57cf125fe4c8ceef2013c41727fd6e6cb67 SHA256: b796450cfaed9c8340dde2eb2056f82a7161e93282b5fd195684f8b7fd1266d4 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.30 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5 Filename: amd64/perl-lua-api_0.04-2.30_amd64.deb Size: 173872 MD5sum: e248497a4948e59326caac10a3ceae38 SHA1: a68484db1eaf4541828577716878f5692a372c0a SHA256: af5ba2b82d4d483128706df670a3c77bfb57a1c6619f298ad39a0b3f544c670e 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.30 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5 Filename: i386/perl-lua-api_0.04-2.30_i386.deb Size: 162612 MD5sum: c396a479cef1ebd700ced0d19cdbdcfa SHA1: 59545006dad77e9e1adcad022252adec72857f8d SHA256: 07c3b403be31988a7c72e4b2a2ad4b390b523cd8865ef6986ad793edc43f7de7 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.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 733 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423400-4.9) Filename: all/perl-module-build_0.423400-4.9_all.deb Size: 251616 MD5sum: 255be2ee06e53198f3665aaec1fe7faa SHA1: fcd7f96e3a45ba1914cbe40062f88fa36ac28d7c SHA256: a12c38354e10ed9ba58822c068225fe08df62e425e20cb5ca4d6c1ea82663121 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-3.2_all.deb Size: 29644 MD5sum: 3b8b41a21e848fe02b0dca6a3ee5a56f SHA1: a74ef7a5331adf98ade5d93c94bcd2371de750ef SHA256: ec5d415ee26fd93157bdecc0ae36b873be5c645433081a75dd6bd5f1ee3fc7d2 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.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-3.13_all.deb Size: 18448 MD5sum: dd38a25750de5faefae10a4a3db0a582 SHA1: 2bd8f653f6fb28b23e90370b3d7ce29d7f9c2e39 SHA256: 0bf36b3d7d5e0a7928bd4f001bd28ceb69f97f9420a94f75d684f8ce0eac3d32 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-3.2_all.deb Size: 17204 MD5sum: 6fccdcc538a2969778cd3e0d799b5072 SHA1: da61e470b68837f36d901da15ca4d93a8c97faba SHA256: 6d9a1f5a23ce21f64805a9484719769b9dcdb99f6d47c5a19b99287966d7ca7d 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.238-3.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 47 Filename: all/perl-parent_0.238-3.3_all.deb Size: 8344 MD5sum: a75881f9abd0127bf4de99ca12b01630 SHA1: 8c33e0ea8aa9d418f26ce85883c5cd7ae6ebd5d8 SHA256: d9dc10b1f3fb7e516382d69066c9d30012dbf092b5bee7ea18184ef36c5b6143 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-3.3_all.deb Size: 15200 MD5sum: d923bcfb96be792bfdd12a80e57281a8 SHA1: 66a560743d4fbace1eac6beffe629d96bed425d3 SHA256: 896f27ff3e3f3a4223b4249b194ffb9ea11485e3ad6c2f906d878769a7ccbc62 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-3.4_all.deb Size: 19124 MD5sum: 801c10c5578290dc0baf01d1629c7041 SHA1: aa78eb8cb063b879945e4a00c2066ac732fe87c6 SHA256: 7fc797354aef5cd3651168a39714b0018c4873574569977e1ade9ffc377dc8cf 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-2.11_all.deb Size: 22172 MD5sum: 9a08cd5fca5f6cc78b43e1b093697d1e SHA1: 76bdffab2a636daa72a94649d7efafbb04c44a0c SHA256: e45f1d13761913b6eef8c8f2028fc2718efd033e99672ffe5662ca332cb3f61c 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.24 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-3.24_all.deb Size: 56800 MD5sum: 1d822630826acd4fec696a467e5b4ff7 SHA1: 53b98db111ef99123fa516db5dafb497de43f250 SHA256: f6050ca1501366f0b4ea9d8573442ed182c6e0a02deac8c6a9da09d84cf34ee4 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.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-3.9),libtest-compile-internal-perl (= 3.3.1-3.9) Filename: all/perl-test-compile_3.3.1-3.9_all.deb Size: 21464 MD5sum: ec457e2335f9e9568a9137f7ad57f9ff SHA1: 1eb9e09e2c1cd05a42e65bc00ae0c74c845e860f SHA256: 61ef3bf48e82fbac7eaf77964c9f277d1fc03908460ddcbfbf06fa58ecb0dc50 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-4.4_all.deb Size: 93232 MD5sum: 9aff784cb898c67b278295352c2a0ae2 SHA1: ac51f790c23100cbd6090cbaf50dc069df8ca19a SHA256: 720bba6414cfa4254c76955c18092c161094fb762ef8c1c4994c26fbbcda8a9e 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-3.5) Filename: all/perl-test-differences_0.710.0-3.5_all.deb Size: 18376 MD5sum: 81c1a37c21b436126f6d3a7914766170 SHA1: e21381c428205bf8ab86af074e1dbbaad4bf9abc SHA256: 11462e0e7bb136dd01369c85764cbd17f4f886b983f46997907b2145d48b3fdb 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.15 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-3.15) Filename: all/perl-test-exception_0.430000-3.15_all.deb Size: 18084 MD5sum: 257ad53974006039a327d9fefd23e6d1 SHA1: 016cced0ed92e919edaf078f07b703519718ee85 SHA256: a415299111e3e63b2490e3ad81190fda81e8b06d45541f92a55ae05d44b92724 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.21 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-3.21_all.deb Size: 23424 MD5sum: 5147fbaad3095749c24931994a5a2fde SHA1: 506bf27764de12c6dd4bff78b7e93651ba492205 SHA256: 2be2a0721cd903b79b6f6fd189feeb7db910b2c62e48bafec75af8ae8e4a4f29 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-3.2_all.deb Size: 13316 MD5sum: 9a2a250732e6a03156fa8ba91a20145b SHA1: 153a96703df509c2cc09c839f3f10541d84d437e SHA256: 5f32cfc0a9ebbe20b55aa6d570741bcf0266f84e421b42cf3dda9da63cb383b8 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-3.5_all.deb Size: 10932 MD5sum: d74328c3e412b607953021e1eb279ca8 SHA1: e69b92bc61b397c91ba409e41e6bb17a6b3c0c52 SHA256: e7d06059f305377feb521e9f52ab3d620f6818360ca7e24fbe5c0fcafbef1f22 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.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-3.13_all.deb Size: 14848 MD5sum: 0d316d3799b1b02ed86c9f26162dd2ef SHA1: e03532ec9d654a2efbedc12117b3421793b9b9c9 SHA256: 1c498bbd8c0c9157079ce2ab59bd9c251f252dbf9b24f6915cadaeaa8e9751b8 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-3.2_all.deb Size: 33352 MD5sum: 73d6d54849d53b06b735979f5ca79c10 SHA1: e3287c6ffef4ce11a0190695ac26f632fafae92c SHA256: e12aab8b4cc02840ea728b7ecd83137649603e2892d5ccb7be40d60b0aa7af99 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-3.2_all.deb Size: 23972 MD5sum: 7a99d06f58177b9512ca55b2d19ee404 SHA1: ef120074336bbef5e6b6c5d6acfcef336274784c SHA256: c9b8673b6a2d2a400b23e31c4280c5913a7762d6112cd2de5733ea9a4447c827 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-3.2_all.deb Size: 8924 MD5sum: 74fdf7be219c2a66d71f3e1e3ff4f4c9 SHA1: 303b3bc41e571af4ec81ac1391c870e97f6cd226 SHA256: 3e4107158b56492ea1d085b28d42adeada1166df92bae93b5b3ed9dd0f425ac2 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.