Package: deb-perl-macros Version: 0.1-3.5 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-3.5_all.deb Size: 2782 MD5sum: e8f88d9c21e9f4b0f65631253f8a276c SHA1: f7626ad5aef8100e9885e2d75d42ea23492f23da SHA256: 880729feaa900d9e2fea5c14012fa4f9ec9b5c185883f256cb0521016693408e Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-3.5 Architecture: all Maintainer: debbuild developers Installed-Size: 153 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_24.12.0-3.5_all.deb Size: 55556 MD5sum: bcf01cac7ce23c4e829734a9c7ebcd15 SHA1: 1f84b3e4096dfbc738b986618f3b7b606f8fc063 SHA256: 1b972a73d4b921cd0e3295c7add997debf96d2cabed2b1e904b49872460117b4 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-3.5 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-3.5),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.5_all.deb Size: 8350 MD5sum: 2b4172441dcc917286ac6ad5f1ce04c4 SHA1: 90e9893e4bd601c9513107ba1639676d0ddc370e SHA256: 2f25c275099bbcd1132e2c324f1a705398a8047ab61b5955d871ce0dbf2e854f Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.8-4.5 Architecture: all Maintainer: debbuild developers Installed-Size: 90 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.8-4.5_all.deb Size: 26296 MD5sum: 7c7c7f4657a34d40641b6adba661e8b5 SHA1: 819b83c9a8bfbdaf1dcdc984a8fb315290bf8e5d SHA256: f6c797494e3e9cfe6f1b7c680cc29a7737ab291620a8545f3c59aa8153726afb Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-2.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.5) Provides: lua51-libs (= 5.1.5-2.5),liblua5-1 (= 5.1.5-2.5) Filename: amd64/liblua5-1-5_5.1.5-2.5_amd64.deb Size: 346924 MD5sum: 1a43582ed979414073b47621d39689fd SHA1: cd1a9e1a012d819b498d235b97b8e7fe7c88dc26 SHA256: 5ee759b051600356bfddf242ecafd8203899bbbbeee13c0ee1f97c207beb3512 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-3.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 1 Depends: pkg-config Filename: all/lua-macros_20210827-3.5_all.deb Size: 1528 MD5sum: 8a4ebd03e581269afb3fb226139a1b2e SHA1: 5cf053fe23e8f263219d572a073bd409cdc1bb7d SHA256: 61d1353c3f896b7c08e209dacd86a0cba6a5a87851d8422159a8545f37897602 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-2.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1487 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.5),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-2.5_amd64.deb Size: 426988 MD5sum: 5c336431d7470682c506322c9e0f60a8 SHA1: d1f9cf2fd76d43c12f02a8cd4dc5d83a8641c657 SHA256: b737483a574dcdd3880ab0e89a38d5a3e8260fbd033cec7b4a48427330d07722 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-2.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1699 Depends: liblua5-1-5 (= 5.1.5-2.5),lua51 (= 5.1.5-2.5),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.5),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.5) Filename: amd64/lua51-devel_5.1.5-2.5_amd64.deb Size: 443040 MD5sum: 28c519e30101378ce5cb51bb9207ee26 SHA1: 196d4eade836ec250ac9b1d8fc828b955334a7dc SHA256: 2381814850dc48fb906069c987e5f71341cb2d3f3e4ed81dc8e532f914c9f3cd Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-2.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-2.5_all.deb Size: 73404 MD5sum: cb883680c02b69a5698d4cdb2d81d5cc SHA1: a3d26dee9f9839b919aa8c0e2177428881a90535 SHA256: 062171485a44f89bb36f6a4f8b7ba8604176e40691402ef28c42a68c9e7e3d82 Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-4.5_all.deb Size: 30214 MD5sum: 043d601cb3560018c923f689a2f94c79 SHA1: b265dcae4f39a4479ec25f0125f996f3614b80c7 SHA256: 63be4cb2d63c3bce7a516fd28528ceecdc0c51d60871bf3cb1f09ede31f8d212 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-4.5_all.deb Size: 22990 MD5sum: 8871e93f3b4fbe590a391c54643e12e4 SHA1: d310428467e1e79d5a87c4605d1d00421f31f121 SHA256: d80975b06f2f3fc31864fe369d9bad0389bbd1e4f7d56b1283e8963b8796c551 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-4.5_all.deb Size: 6990 MD5sum: 615e21ef8d9cac4c398d991a2c763af1 SHA1: 0b0ad1a6cfed4db3d9b3ccc8e967abf132769cd9 SHA256: 58d4d0ca5d8549f2060d48c2e5093fc2716426824f2d35d8a70bd729e0872b08 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-4.5_all.deb Size: 28324 MD5sum: 18f3368acdcb786d96d44c11311cdfd6 SHA1: f17b28e94dd03c093468e32fc4b7a9f7b9dd9e3c SHA256: 8883d2005f8c90d26bd778c860b61ac78531afc2a4bab58dc027891cfd6299fa Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-4.5_all.deb Size: 14518 MD5sum: 0a1159ca5642f4bf59084648cc6d8cf0 SHA1: f90e46d151a2f1628faddb85cb9c6b15c78f171f SHA256: 4a54908287d70bcc08b13091e512bfcaaa777047eeb6b312ca1271754415bd43 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-4.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-4.9_all.deb Size: 38950 MD5sum: 7580ba7316b924035dce83caf3671298 SHA1: 328fb2f87875fe5ce5bc13049cd99c8d618adcab SHA256: 1496853839b35bbc9d1fc58155d1bb2cf943da6a58baa92991c599e1b80b355f Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-3.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-3.9_all.deb Size: 39284 MD5sum: 0b84165e4eb8ce7e8ca0055f3afaa821 SHA1: d4447c4407ad6c4939328fb8c42887a3bf1d5b01 SHA256: 72eef4b2da961d169d6b443ee5275e6cbf6c75d2d554857954080344c9054a8f Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-6.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-6.2_all.deb Size: 298016 MD5sum: d8391e26f27722a55a9694983edec793 SHA1: 5f8589d474b2d8f148ee8639eb19d67147b2cdd9 SHA256: cff52aab2210349b8ad7004e2e8a57d96ad7ee1db763cb3f4b61e282294aeda0 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-4.5) Filename: all/perl-extutils-pkgconfig_1.160000-4.5_all.deb Size: 10464 MD5sum: f32bebd2da7818c85c43ef5db61b81b1 SHA1: 1a98b365953550e1985d7ea364cdd474edad5199 SHA256: 1167e30a8ab65506acc4246c21f6850c155bc970c2e888ee902bff1d1dd03e8a Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-4.5) Filename: all/perl-file-path_2.180000-4.5_all.deb Size: 30602 MD5sum: a041bb25796beeffd0cdb509e2de8139 SHA1: 1aaa4cbdbbef6a1a1db979c3ffde1d09efc063ed SHA256: 06367b369be1526398c63ac0e55fa4a1fed290b04f29f2ff75a213476d3b1555 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-4.5_all.deb Size: 53842 MD5sum: 62b147a5b0382c409a4f24428dd25576 SHA1: 943b01c455f81eb8f89dd572fd28a682b756b405 SHA256: ad1f2b41146ad422046890fc0c5ccc31211f94f3eee147674b98441e14fadee0 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-4.5_all.deb Size: 33230 MD5sum: 89f4ea4dd49f4a3dd69b6702b6966ab9 SHA1: ac8dc3aac37ab7e90f13c875bf3e2f3d5b8dbb78 SHA256: 5583c9d058bdf8a19a23b8c83b5c7d736d6d0ecb90c706cbc8183be1f65f8893 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-4.7 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 719 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-4.7_amd64.deb Size: 216846 MD5sum: c3112a06704ff939b14a4aa2ae5cf99a SHA1: 00bd18023ee8aba81207b01b3b376e086b3922b6 SHA256: ea718e6ca1b2adefb75c821ab9bf871fa6c34fb2d4c0772948e747c464dcb9ff Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-6.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 657 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423400-6.4) Filename: all/perl-module-build_0.423400-6.4_all.deb Size: 234610 MD5sum: f0ce58ebf606454fea16de311b7aefd1 SHA1: 3e4af4f261d055187b6e578e07d33da6fad0da19 SHA256: 65dc3524cde0f6113eb1054b5665608700523ceb5768f2896d2ece0a89f74661 Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-4.5_all.deb Size: 30066 MD5sum: a9947d1d102befb34de41adae741da14 SHA1: a389841445aab9c261e4e4e064b1678883739bc8 SHA256: 1ae6a4ff41fd4919bb7d416432b9afafb0c81a9b456f3590d59efd84e9bad667 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-4.5_all.deb Size: 17716 MD5sum: e457fd532377bbee217146a422b071ec SHA1: cd725dac67f66450f5f2d7a8e126a2925c4141a7 SHA256: b6fe68c25b32e0400f341cb5b4efb0b1758dc9fef691c3c9ba4a76c27b672212 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-4.5_all.deb Size: 17510 MD5sum: 610e53d9cc59e35c360825c3992ed182 SHA1: 68e528923105156ae5a708cfb628696c36adea2d SHA256: 33a00ba44a395b11f34bbecbafe7893fb3d3dd01142036128b6e8b13c1e1b34c Priority: optional Homepage: https://metacpan.org/release/MRO-Compat Description: Mro::* interface compatibility for Perls < 5.9.5 The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. . This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). . It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. . If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. . Some parts of this code will work better and/or faster with Class::C3::XS installed (which is an optional prereq of Class::C3, which is in turn a prereq of this package), but it's not a requirement. . This module never exports any functions. All calls must be fully qualified with the 'mro::' prefix. . The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other useful information. Package: perl-parent Version: 0.241-2.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-2.5_all.deb Size: 8754 MD5sum: e2ce6991ac5808e6492a5b0eae41ac4b SHA1: 5f4e836e96911d91763ad827acdfe6896b780966 SHA256: 4cd7c0958edc5b4e60904934ece4bdf0d42a274faa3de8486811ebcf8d22558a Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-4.5_all.deb Size: 15490 MD5sum: f7ba695e8c1569d300482962af9e7f1d SHA1: 10606544bc2a4f5e0cb95e7bb6b3e5bdce2efede SHA256: babca8d1cbbc5df1d4f6317eee7213b904f343fa6fbd5cdc4e16682dd4d6984c Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-4.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-4.8_all.deb Size: 18482 MD5sum: 9e1d8b05532b9272b5e77918029c395b SHA1: 2a744a835ca7bdea8b73ed467534e07371582a87 SHA256: 8bed207637bcf79efa1fe9da6f5c7536cce6a189335ac58360e2218230ef313b Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-3.4_all.deb Size: 22432 MD5sum: c3d75954b16a37784ba189d0e56eb32b SHA1: c6b5ed4d388f629bc60b01495530c88fe4f2ca61 SHA256: 47eeb2653be7ed6916a9b51ca0c98dc7e091ce968141534b885196dd32682eda Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-4.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 163 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-4.7_all.deb Size: 56430 MD5sum: 3fed509e28be786e6ff0eb8f18a583f9 SHA1: 66f797f3f95cbc0fdf810b5346b3582d813a4a23 SHA256: 22bd05b30eea7455d0702bb5b9a2c34db592793234ae0c6c55fb255c925668db Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-4.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-4.4),libtest-compile-internal-perl (= 3.3.1-4.4) Filename: all/perl-test-compile_3.3.1-4.4_all.deb Size: 20040 MD5sum: e4e169c9e1b9288be2afb75e2013626f SHA1: 5e32938dfba907b69652573fe47b59505bd0350a SHA256: 4d7f7c75ada162f9178a644087acd2668a1e390d83000e7ba2ca79ce6ae8bfba Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-5.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-5.2_all.deb Size: 88600 MD5sum: 8ae1eaec4caea08d064255db322f80fa SHA1: 61646ddbd2698c15ba4f43fa8f6c08a583890a3d SHA256: 996881a7781b91115cb5c9881c59148082c4f11b2204a8407d64593540f93802 Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-4.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-4.9) Filename: all/perl-test-differences_0.710.0-4.9_all.deb Size: 18552 MD5sum: 3ffd74d6995d60e432b31ba15bd56f00 SHA1: bdcb741b6e4c37d50fd37c64d51c97831381739e SHA256: 2d997fe87cd905ccb7358f51d349af41495d0f3b69af75fe21f2f201d0bff4ff Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-4.5) Filename: all/perl-test-exception_0.430000-4.5_all.deb Size: 18226 MD5sum: 7bf6f63a4eaf61406b0d9c3370721767 SHA1: 36a9af2f48553574151fc8a31ecfbe4bcb34778b SHA256: 7886427ea77712edf8613f6270eb5b44686c6a3b41e62c93f066b9e3774fdbb4 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-4.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 42 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-4.7_all.deb Size: 23412 MD5sum: bcfc42ecf4707a53a773b81c6a506823 SHA1: c7d6ada7f8cd00118036b5f386b1cc943606b025 SHA256: f1556211f6246cd534f3029b55c8d3a744aaa45f72eb704526c345cece1ec946 Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-4.5_all.deb Size: 13380 MD5sum: 031850830357ede4fbb780ba455acc10 SHA1: 0418a7ef5f561cc8caa08b02ac039242f92bb622 SHA256: a8af27c3fdf78406e1a0e1a36e766de6c056960a14dde0db48ca09d30b07ea08 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-4.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-4.11_all.deb Size: 10800 MD5sum: bd84c47fd1f67a03cbe02145fad1d9b6 SHA1: 7a6ace73640eb7da470e4fe2b97114e04b9981a5 SHA256: a49743d9555ca5ded8e468b8f81c8051226b702abc2dbb371e1e6fa71a518c9f Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-4.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-4.4_all.deb Size: 14822 MD5sum: f6e27bd17b5f309090123455f6e8bfbd SHA1: 71e551886415e70096bb9823a3f0d966f2dc73d2 SHA256: 28b0f2b51d1db2f720055cf601a999d7f6acaa57d0474aabec2d470bb107c361 Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-4.5_all.deb Size: 32924 MD5sum: 6434a0c527d45b833a12c6a9c0554051 SHA1: 66670f11271495a5dbb6cab4cd3eda046ea29a79 SHA256: f3be30f42938620a8f1700699500f8fd67db7ce87281a6f71f3d0748c34cf866 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-4.5_all.deb Size: 24322 MD5sum: 07098afaf761532a090e2570402e6b68 SHA1: 77d203bf971c9874b8d320a2024ca0ccef2d24d2 SHA256: e2dd5cef9742ddc6923d876569cfa4de5aa922d1f6104fd92632e5017d7d6dda Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-4.5_all.deb Size: 8700 MD5sum: 08176d9a709400d6153326752e06388a SHA1: 6de1f8683b8c380c16f52ff0d4fb3698a066e085 SHA256: 231ba62cbef1fcc1dd7b8569ecb65798cdb501f2f8326fc5b65b571391da30f6 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.