Package: deb-perl-macros Version: 0.1-26.5 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-26.5_all.deb Size: 2626 MD5sum: 0f35c6a99aa6793eb68ed254f90505ea SHA1: 44128e1185aa1e039c0f5a20baada51b8dc93f41 SHA256: 0f6c3cd535dfe960d6f1edc33e3160283e0c85849654664334005def88ac967f 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-39.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_24.12.0-39.1_all.deb Size: 55042 MD5sum: e4059801e004b5e73b07b38a384e2beb SHA1: 0a22bb661983b916c24e341237b75c1341456466 SHA256: dbbb7c785d335cbc51e3a542346ae58485187d348bcbaf61beb60700dbefa4df 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-39.1 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-39.1),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-39.1_all.deb Size: 8552 MD5sum: fc442cbb925448e85b86098b28b90e82 SHA1: 8628a1a5aa439ebba5ced8d535f8a6078a51170f SHA256: de0723730e9567504e7c6870a92fc00c6c6f5d55045fdc94bc9d7c0b6dd06c21 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-17.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-17.1_all.deb Size: 25408 MD5sum: ade450decefbb28b47e15b5228f88ce9 SHA1: 9fe9df3f03447e71737c56eec827ca042197f312 SHA256: c2bceba345e8ca405fc5f5630c72dc72a797d07e8a91164648567fd11854f0bf 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-71.4 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 679 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.4) Provides: lua51-libs (= 5.1.5-71.4),liblua5-1 (= 5.1.5-71.4) Filename: i386/liblua5-1-5_5.1.5-71.4_i386.deb Size: 235196 MD5sum: 3033c8b32289c32acd90c6ff3b35351a SHA1: ea99bdbcc4994c375e15a351467b138eb6a55762 SHA256: 8c47e4053662dcc2f8df4cd600c40e288faa03c54c7f71e3f1a3dade25bcb67f 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-71.4 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 867 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.4) Provides: lua51-libs (= 5.1.5-71.4),liblua5-1 (= 5.1.5-71.4) Filename: arm64/liblua5-1-5_5.1.5-71.4_arm64.deb Size: 225976 MD5sum: f73ad5e58028fcbc6507ccb949c197a1 SHA1: 9f595bffbecfe96e01e7d89508bbb8079aee4cd1 SHA256: 22b7bb98effd17dceb5b5f569ddf71aa7568b63bed89a4990c2ae7622408fd6f 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-71.4 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 629 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.4) Provides: lua51-libs (= 5.1.5-71.4),liblua5-1 (= 5.1.5-71.4) Filename: armhf/liblua5-1-5_5.1.5-71.4_armhf.deb Size: 212076 MD5sum: 372b5785fc67a87cea9c63fe2f2d0f3f SHA1: c819c1f29e57f385d9796d4e9484660e58a44d94 SHA256: d5d6a9c4d15ad1dd1587dadbac9066c15980f28b86fdb52a1910acbf95c3b982 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-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 842 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.4) Provides: lua51-libs (= 5.1.5-71.4),liblua5-1 (= 5.1.5-71.4) Filename: amd64/liblua5-1-5_5.1.5-71.4_amd64.deb Size: 237140 MD5sum: 6ed3d7bfcf6acbebdd8c1290837ff20b SHA1: a95394bc8375ce60c79b579311c22832cc59c7b2 SHA256: 931db1b678bf4463500f0563211414132a0348b47c23f837e70502d3a9f93213 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-36.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 25 Filename: all/lua-macros_20210827-36.1_all.deb Size: 1448 MD5sum: 865a88a5e8d5e19235fd9f1ea55f5064 SHA1: 19a6a4686727e57226781858c0fa84acdcd68cb4 SHA256: 73a78bb9a0fd91ac24d037d9eaa17c2f59276ed8083fdaf426543437b9686512 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-71.4 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1177 Depends: dpkg,libc6,libreadline7,libncurses5,libtinfo5 Provides: lua (= 5.1.5-71.4),lua-api (= 5.1) Filename: i386/lua51_5.1.5-71.4_i386.deb Size: 287594 MD5sum: d7072ef0f8725ff3304e6d5cc47be600 SHA1: 2b759ff443385e309b87618d7c92e92945deca79 SHA256: 62ce8d997972d90308904d68207828e2e29e0e4b81e86a4d1f77536ead578f5d 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-71.4 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1513 Depends: dpkg,libc6,libreadline7,libncurses5,libtinfo5 Provides: lua (= 5.1.5-71.4),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-71.4_arm64.deb Size: 277168 MD5sum: 21452627727fdd35153613f652ba61c3 SHA1: 2c0694ada17864f414812fe100d018566aaa6eb4 SHA256: 3ef3f6ac58e511bb00edf3972b5813f57ab3efa881a7d1fcf62be4850efdb35b 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-71.4 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1098 Depends: dpkg,libc6,libreadline7,libncurses5,libtinfo5 Provides: lua (= 5.1.5-71.4),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-71.4_armhf.deb Size: 261482 MD5sum: 2a382ec9eec660492f97aefd5ceee961 SHA1: 3a8ec6a107d46b00fdd23a08cd8383b8959bffb4 SHA256: 4d1671cedea0d551ac03a2222b7ecefd3e2c76033e8a95fda6069b90542244ba 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-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1463 Depends: dpkg,libc6,libreadline7,libncurses5,libtinfo5 Provides: lua (= 5.1.5-71.4),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-71.4_amd64.deb Size: 288998 MD5sum: 0363ec1f8425e3cbe61679c6d0d3ac9e SHA1: 899c1e40e5f166bd3d6d9ce1333a6f4b7a6feab3 SHA256: 266ef321897457d8af27b7b75d0cb189d12e7b163fad50cb9bd6efceb4c23731 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-71.4 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1012 Depends: liblua5-1-5 (= 5.1.5-71.4),lua51 (= 5.1.5-71.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.4) Filename: i386/lua51-devel_5.1.5-71.4_i386.deb Size: 303846 MD5sum: f068e69560556377770fc438561e959e SHA1: 1e3aec2792a7b6a41ac5ff712dc61498559b31f6 SHA256: c79766dcf5c47ab633ec3389f1819e6a4c54fc0b63ac0bad022459ca2685bcdf 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-71.4 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1535 Depends: liblua5-1-5 (= 5.1.5-71.4),lua51 (= 5.1.5-71.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.4) Filename: arm64/lua51-devel_5.1.5-71.4_arm64.deb Size: 300068 MD5sum: 6c832a16fdad7ef679ccd50be674fdaf SHA1: c4f4b0544e5f471e58bf0e5127027b3c5c346741 SHA256: c0dcfd25ec22be816ca8bc97c793340e7b442faee36284f8ce4cf40283324e8c 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-71.4 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 946 Depends: liblua5-1-5 (= 5.1.5-71.4),lua51 (= 5.1.5-71.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.4) Filename: armhf/lua51-devel_5.1.5-71.4_armhf.deb Size: 281632 MD5sum: 1701f5644c036f08dea44f163fca475d SHA1: 574ec9ca16e50dfacc24cc9641799dc0b67c7bc3 SHA256: b91f10227ba4dbd7bb70b8788b879d736b62911cd15d0152e85b78d95589a116 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-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1499 Depends: liblua5-1-5 (= 5.1.5-71.4),lua51 (= 5.1.5-71.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.4) Filename: amd64/lua51-devel_5.1.5-71.4_amd64.deb Size: 305974 MD5sum: abfef575eebedd5b0d6c474183c046ee SHA1: 77d46e49945d249262d7a184eef37d13f528c5eb SHA256: bad8b8f644d871a514df2782d90e12adfcc0abb1a7fb8804c8c3bf9a24bd1b25 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-71.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-71.4_all.deb Size: 71582 MD5sum: d63b5dbd12b9fc7a069b8d8b0d7a81bf SHA1: 4e3d240c0221eb3b5294607818a9058f89841620 SHA256: d5743fae9a3aa151ea2984824b7ae8bfbf84913d885e39a032055656ba18426e 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-26.4_all.deb Size: 29892 MD5sum: d02c21e97c45246821633f7f7a544978 SHA1: 76eb77ad47fd8253fcee203175f793b97b1f793f SHA256: 8af30e7bcc30c4489a6081884f2d649b73913748dd89ecbc0d497747ded3dd9a 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-26.4_all.deb Size: 22582 MD5sum: f13fb5aa6bbc17d3edf47f5b4064602d SHA1: 6dee27429e8248a4c096c504d5ae77737bf25412 SHA256: fd1ac59ca121c54c768cfe2a277a051ef4cfbd2a6526c44558c9fb858626031d 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-26.4_all.deb Size: 7124 MD5sum: 906a77fed492bd5fedbb90ccada02705 SHA1: 7b69d6ac497a8eea9f03d46a0907c1c5a3768f2d SHA256: 07f98f754b3a0edb74de3f12e8ce4832e6326a67967db99374e062aa1b639465 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-26.4_all.deb Size: 28252 MD5sum: de98d347d8a22fc930896f057820e857 SHA1: 2d119b7eab90891d57cf82e37352b9da97f35ad3 SHA256: 732f4d96402d988429e54015908df1f3ac13220ea234dfd356f9a6087e41c29f 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-26.4_all.deb Size: 14264 MD5sum: 9ea6f57928bf6d6de82d323870c05f67 SHA1: 055aedc1dc50221961eefb980a222e19222f9f08 SHA256: 9370e94af35c0ba09f977f4bc6ff30cf2cbb39ad09672872fc584a7b40cbda7a 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-26.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-26.9_all.deb Size: 38900 MD5sum: 849717707d8e99c64bbe8059e83158e0 SHA1: 5f0407670c9fd5e4b951515c64a95bdd1f1fa9f1 SHA256: 02f780c6ed96f8285faae8041499fdbe83cca35b71cd013e07420e0d55e38ccb 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-25.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-25.14_all.deb Size: 39108 MD5sum: f3403f0a00cd1046dc81291924ed6156 SHA1: c66938a830b7450f6c0e99de144cd0a8360952ad SHA256: ecf99abef0198e9b819e937618e47761ffee562e0bf1b7a0d3b9c51413bcadc5 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-11.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 889 Filename: all/perl-extutils-makemaker_7.66-11.5_all.deb Size: 302998 MD5sum: b5a8e40ed08e7f31d9b93247c471d4ac SHA1: cc6a6054be3eb393bfcda9bad15172b294be594d SHA256: 25510447448d2ef84f5faa14d45149b59c1d7a0703dd997c7832b5fa735a6d3a 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-26.4) Filename: all/perl-extutils-pkgconfig_1.160000-26.4_all.deb Size: 10432 MD5sum: c7e7bfeb028154369bc45e2c982f1fad SHA1: 6c3d5942b126317635e3d24a2b1bc9e74dd2e531 SHA256: b8f3d86a9bb9f78f88c821db76528e9f92303f0f13e2766585a76943ff10858c 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-26.4) Filename: all/perl-file-path_2.180000-26.4_all.deb Size: 30540 MD5sum: d346aa91e3c3b2fc568c527f8cc1c6fd SHA1: 8ab5f9aaf512453902f4867f0d7546167939ae79 SHA256: c940fadd3d87d8db14ce0266d095c27ba905902d35496eec1d006b93f9da1fae 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-26.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-26.6_all.deb Size: 53182 MD5sum: 88a15d37bb4088e871d887e9bdbf0eaa SHA1: 44498a71e8dbb62d6be8fa3b687f71efb443e32c SHA256: fefe45b97e5966c95b8cfdf7520d2f683e7c10e4ae9cd725814f5a3c6979e548 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-26.4_all.deb Size: 33046 MD5sum: ae1c136a72baa227dba3751fdbcf477b SHA1: 1e6ad336a03a0fb0965e16a0d117abaad4f0abd3 SHA256: 37b922c6d31372341da4f2825953e82d239887bc9bc19acb8cb2a9228f9561aa 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-27.60 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 651 Depends: perl-base,liblua5-1-5,libc6 Filename: i386/perl-lua-api_0.04-27.60_i386.deb Size: 160086 MD5sum: fe4612bcab071b07192d1cc53c6b189b SHA1: f777f6b57eac9206c82712b080c66ce0f2eb218f SHA256: fe4202c2e14c13ffaf34aff8045ac15a3fc6bd5f48373e3a251e363415411dcd 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-27.60 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 745 Depends: perl-base,liblua5-1-5,libc6 Filename: arm64/perl-lua-api_0.04-27.60_arm64.deb Size: 157696 MD5sum: 3f4204906174891cec4de1266b6bd1f2 SHA1: e9b9e7a2e8f68033041a7f14252234b1b44fc49e SHA256: d1cbc9146a18f78c52cc0f0ff4ef417bca75d31c292276a45ef19df82add7169 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-27.60 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 591 Depends: perl-base,liblua5-1-5,libc6 Filename: armhf/perl-lua-api_0.04-27.60_armhf.deb Size: 155988 MD5sum: 9ace5cc24a99bd5c984954c2f5e4b686 SHA1: c4a4686ab7ef8af25f1a3ddd556a94a916b096b0 SHA256: de31318dd877c5845ec84f346befb65e93beffd7102fe8f10b65ee5cbf64f1ce 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-27.60 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 773 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-27.60_amd64.deb Size: 168368 MD5sum: 56a3f4a3d1ecd45920331dfda7a73f63 SHA1: d7dddd4438e0989c9ecf5c1466b25b568c29eafb SHA256: b5eece35e626e11d08611d18cbf018147dd17d4ac8972b6fabb954968fcbd2a7 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-29.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 732 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-29.16) Filename: all/perl-module-build_0.423400-29.16_all.deb Size: 250318 MD5sum: fe246f141f6112a3c630c21ad470ed5f SHA1: d7e0c47dee98131494bf8225f61d281ba33ccac3 SHA256: 24dea1e97b9f4a2b418774094590d94fa95d9cf7e3963944fa537174e0f62d4a 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-26.4_all.deb Size: 29554 MD5sum: eda557e569cea10b99cf245a894181e9 SHA1: 2e4af9d9380be73da5b4ed411293695823ab76f0 SHA256: 46c4e84eceda5ce14c70f1defe9368e7961909fa9cdbeab4bf239f1dff4a4b90 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-26.27 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-26.27_all.deb Size: 18314 MD5sum: 1404c0ca1b829484249ba322643c0ed6 SHA1: 2acb168653f74eb3b6e8c13d043190471486ecaf SHA256: 58316b9598193d0367f1ec52c53e32c6e15cd4ef918c05b482ce22b490a8ae96 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-26.4_all.deb Size: 17078 MD5sum: 15b153f2677421093300e6aa9e46805d SHA1: c727d5af5d7cccb47f2f1dab7ace8f7c3d9aea9e SHA256: 529484918c308c95befd25f57a90daa1489fdead026a3f4c956a79380e340d43 Priority: optional Homepage: https://metacpan.org/release/MRO-Compat Description: Mro::* interface compatibility for Perls < 5.9.5 The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. . This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). . It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. . If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. . Some parts of this code will work better and/or faster with Class::C3::XS installed (which is an optional prereq of Class::C3, which is in turn a prereq of this package), but it's not a requirement. . This module never exports any functions. All calls must be fully qualified with the 'mro::' prefix. . The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other useful information. Package: perl-parent Version: 0.241-1.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-parent_0.241-1.4_all.deb Size: 8754 MD5sum: ed470118e0050a59a115dc0ae61924e2 SHA1: 019f164f7c5386df78f4960f5edf853e1f5dc38a SHA256: a17db29bb550a0e8dea762ce43a6f764cbb60831cefbd600f799cb87168fc339 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-26.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-26.5_all.deb Size: 15076 MD5sum: 7fd79a300cd01a6f8640a475b6e7915e SHA1: c113719133ad29d4e64207df233ee89c08747d01 SHA256: 093f72ca71bc1cd0f190a851777c4086fb9dffe6286759a1a874c085306551b0 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-28.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-28.9_all.deb Size: 18900 MD5sum: 783a17bc5db136589dd791db0711459a SHA1: e549c7b0b4cbe689926a210b9fd3f51466cfc4a3 SHA256: f2123b4d560bcd27388be1b286226b9126b493a039262a25633daf1c57b87b8a 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-25.30 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-25.30_all.deb Size: 22058 MD5sum: 13029d81a7759dff339e5b43fe73d081 SHA1: 98a28c59c48a7459ceda4428c91fe71d5c7ee8c0 SHA256: 8d3fbdce093533aec1faf6eb48b18813765fa0d4ff616524257713031e1183e6 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-26.44 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-26.44_all.deb Size: 56636 MD5sum: f2702b1cab8fba415790a58fc239989f SHA1: 1fe72b6cf0e9c9939f4fda7e8c229d5f14e0ddca SHA256: 082327b6b57bca0c65df154d323ac5ded86efa918a71d5b263506d94e26a300d 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-26.24 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-26.24),libtest-compile-internal-perl (= 3.3.1-26.24) Filename: all/perl-test-compile_3.3.1-26.24_all.deb Size: 21288 MD5sum: 82cdaa87f0ccb4c4396db4c408ba55d5 SHA1: 73cac007f6d6c9698f2b3c88a2af292ca1b76d32 SHA256: abb7462eb028c5a7d3c704a9c90b7d19bb875c36900ef675943afa8278af1c4b 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-27.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 352 Depends: perl Filename: all/perl-test-deep_1.204-27.9_all.deb Size: 82120 MD5sum: 164cbb22db578db9f02184d2c0235f9b SHA1: 2030cfc4cdfd6cf87b33d27b529fae69afb1412a SHA256: c09c6b9b355255da789ff24712f32147eab15edbfd4ec0f09bb24feb4dc56139 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-26.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-26.12) Filename: all/perl-test-differences_0.710.0-26.12_all.deb Size: 18284 MD5sum: 5ab603563c94962b557767828bf6d22b SHA1: 9ee4da491d9c2474c728edc13cbfcbb5f69dab16 SHA256: 950b8bd0fbe8cc150e1e7685740071353598e750a4720354c271fecb255972dc 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-26.33 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-26.33) Filename: all/perl-test-exception_0.430000-26.33_all.deb Size: 18018 MD5sum: 45cfd77026162a8f1b034a458f1109f9 SHA1: 3f0f18ea2bcf5a7fe35ba689af2b625d7b53848d SHA256: 20c7d55c2a2ef268818c04555911c6a3e01fa439c3f455999f5a61d61593dff1 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-26.47 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-26.47_all.deb Size: 23274 MD5sum: 852b4d86344015e3c3f8d427d5fe86e2 SHA1: 4200ef227324e3770bf7248a51dd3a6e4b684736 SHA256: 1e4658ae3ab1d288b130720fe46c64418d4cb41d2fd6927f3c62279de403a4c6 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-26.4_all.deb Size: 13210 MD5sum: 25434672ba298bd9815610907138a741 SHA1: dd51dc0ac5c0afa5b6311ebdedb72348d511200a SHA256: dc49bffa9558f39695b1f35c1609df789d3b0a0c32e3fec61269f49aa9b515da 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-27.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-27.14_all.deb Size: 10814 MD5sum: b0c5cab12c2fc849a5978105b64bdcf2 SHA1: 1c8a0b90e8b2b1c223475d7dbf9c01d6a958063b SHA256: 9abe386bcd08fabe887f611bb739ac52af8abc40afc8b17d3d4a339c106b24b1 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-26.34 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-26.34_all.deb Size: 14726 MD5sum: 132ec06cbd56def8d72fb65398df93b5 SHA1: 0196f0f21b40c95ad427585815ce201bad137534 SHA256: fef0a34c93a5c2f1bc13b399005da596c84dec3ed493d4f380721c3d11e8e288 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-26.4_all.deb Size: 33162 MD5sum: 879e10af44e7138b401aac88f1216404 SHA1: ba5d1373d85fa169cbf4388e25e1db3d2baf9cd8 SHA256: 786a88146127d2878d003bd936c31b9bbdddd0f8062bf60c1c32e5ffefa87042 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-26.4_all.deb Size: 23860 MD5sum: 9e3ab81594638ddecba8424e25adb3b0 SHA1: ca7b4dea6df709ccba4239df8cc8d25ba552d929 SHA256: 11a676aeb6b14074d49754b7d247ccdda29f4b123baedb9f4ef52c1f748579c4 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-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-26.4_all.deb Size: 8786 MD5sum: 3d5cdbaf0c6aebdf323a8c031f122a5c SHA1: 8cd492ae99596c089472c57393e3eaf0ec5de53b SHA256: fd83c114705e8a04b324a28ca7acd2de14cdb11a8f229337ce8e312057e25889 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.