Package: deb-perl-macros Version: 0.1-2.5 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-2.5_all.deb Size: 2704 MD5sum: dfa9b6a9f1c74c1781c2a2a3087d4476 SHA1: 0ed836d8dd53ce1895069425c8e9e9023fb24bc3 SHA256: 68bbb6084d2a293f2ad538cdf30b684cf099bb185a2359c61c7923cbee8e9d28 Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-3.1 Architecture: all Maintainer: debbuild developers Installed-Size: 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-3.1_all.deb Size: 55136 MD5sum: 82e300160623fe6a85e299827f2c1012 SHA1: 4de2e12b63d21e2d44328563b0b0a6feae99af84 SHA256: d0d2005751c4452bfe378c0da45bbc4612dda0c6977a963b6eb4b6aaccb3361a Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-3.1 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-3.1),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.1_all.deb Size: 8624 MD5sum: a1f5031a266b4fca5ebe266292b108bc SHA1: 8bde64a4f6ab46b37c81227f20df67ab522c9679 SHA256: 23d6687d7d72075d483973ecfd810acb18732e3ee54b4a461c8c778a240f7691 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.7-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 126 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.7-2.1_all.deb Size: 25504 MD5sum: 5e819cade89b2fd918df80a45cab7d50 SHA1: 610d2e619e60b3465a014f332172519918e715ed SHA256: 703cfb4a793f9b9704978b7681ff53d719383175838caf33aff696039523d76c Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-45.11 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 856 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.11) Provides: lua51-libs (= 5.1.5-45.11),liblua5-1 (= 5.1.5-45.11) Filename: amd64/liblua5-1-5_5.1.5-45.11_amd64.deb Size: 243800 MD5sum: c8d4dde76896006ac7818d4deaa5ab85 SHA1: d16aac19aae3a371e03f48d1021beaaba1df1b8a SHA256: 8ce1f5db59cd0e5d1c30b171e14127aa8ac22a825e7417e4d55f9cf26edc72a5 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-28.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 25 Filename: all/lua-macros_20210827-28.1_all.deb Size: 1568 MD5sum: 834a2166e8ccc2ff8021eb905f4f8bea SHA1: 1ea829b6d68e07d2f1f6e78c22a0eeac9cca7ee5 SHA256: 77074bea37179c43569a591c1f598f31019272d7e4eae3cdf81c9a90d2ccfd9e Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-45.11 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1482 Depends: dpkg,libc6,libreadline7,libtinfo5 Provides: lua (= 5.1.5-45.11),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-45.11_amd64.deb Size: 296936 MD5sum: 4c72926b2ba94d4717429c26d38375af SHA1: a0e33d31499c7baeaa9cc9051f0ed8601f5bf13c SHA256: 4831e09c1d9c8447b7e4b4ef9d5e123fef0b900c103d0888c916acc823710382 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-45.11 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1529 Depends: liblua5-1-5 (= 5.1.5-45.11),lua51 (= 5.1.5-45.11),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.11),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.11) Filename: amd64/lua51-devel_5.1.5-45.11_amd64.deb Size: 314012 MD5sum: 992938a684a2f22e49a0f4423ac1b0e3 SHA1: 6b675193f1852e33d2c4b76c58b93c2d90a88e1c SHA256: 8496c69a09cd44b434377a898141835bce31206cb65e00f457e16218f9ff7339 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-45.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-45.11_all.deb Size: 71636 MD5sum: 2567f604250456d5089413a5e091386b SHA1: 6810126355685c1d14542ddc79825dfb94122d17 SHA256: 0113a17c780bc70b8397175ba70c417b20d71ba44585821f0e31c8cf4fc3cadd Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-3.4_all.deb Size: 29964 MD5sum: 6711dc1f8029a731a01566a783c28720 SHA1: dafefd150c869137874f260f8a7b51e24d040adc SHA256: 4a2160f5016e1445e34dcf7d353438604f7fec00bf86489539d1459e493b3478 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-3.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-3.5_all.deb Size: 22644 MD5sum: 82b19caa02231efd0d9206d2e2e9f07a SHA1: fa89b2abe77c0b85a3bdc978c1ab69f01612546d SHA256: 3e747a0feb8ad1ac357061743e8d85cd04741a2d5c1295f252f5d30477af1b55 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-3.4_all.deb Size: 7204 MD5sum: 4100b8cef3958472cf1174f7dc5b7a68 SHA1: d5fa113047d95541372fe7048a1658ddb82ad983 SHA256: 2689714a7227f0ed3bba9ef5890df958149e4be568af99a839d5f0927747c518 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-3.4_all.deb Size: 28356 MD5sum: ffbb7731750c1b09386e7d0961154b95 SHA1: 91d839d75e028ecdb6f3bcc4c7b08eabfbf71238 SHA256: ab8faf3228b7bc4a7d44f8860f6bf8078a803bea3a1c0a8db5d3d54987d74e5c Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-3.4_all.deb Size: 14340 MD5sum: 11c3200569817709954510add809c36d SHA1: 5e1f3877fb8671eaa32565061c9c308ab4b1bd2f SHA256: 5c51b0e9e4ec48533f94d8e6cda8ff76fa5a4c9dcc95302f502b254c8a57d70c Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-3.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-3.8_all.deb Size: 38976 MD5sum: 8c29b4eda13bdb4fe4f7c8ff6b89ebdb SHA1: 30981eb2dff3d4aae03fbb83924c47db6251fb0c SHA256: 1b6661935f1568f8a8c0bccd66ad94f317778c74e293f44238b75a0510ad71b0 Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-2.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-2.9_all.deb Size: 39184 MD5sum: 0cccb05a6d753db3383057304e68d591 SHA1: 145ecca3faf2a07f77510878f1c31112e8152261 SHA256: b7ccb8cc5d5f0c7f205bfc6dd9d1cea79f0f02e99dd5064465ee06c4e8779aa4 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-4.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 889 Filename: all/perl-extutils-makemaker_7.66-4.5_all.deb Size: 303128 MD5sum: 10cbbca917affc6d16f2eb9a0e04fd05 SHA1: 30fc297874dced5815292740aa5e666916f0fc40 SHA256: 9a9b1fb9ceb2ded8f327fb40884c37b69e3122c623630012f48f5e7c2dae0a7f Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-3.4) Filename: all/perl-extutils-pkgconfig_1.160000-3.4_all.deb Size: 10528 MD5sum: debe65977a3de25474b8023bb02628c3 SHA1: 75ccefa78e7ad1472c945c53f940a6db9c406733 SHA256: 8ae68df0aef4a8e2cad2a42da089cf01a9fa9ec121091f9db55b95189cb3c0e3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-3.4) Filename: all/perl-file-path_2.180000-3.4_all.deb Size: 30636 MD5sum: 44eb824a19e4d3d1c49823d3ff03d0ef SHA1: 4be7c638877d9b5557513925c4ad510c7d6c8259 SHA256: 1bf29a97cdb1a810e4ba9a21d8c6b300e9807cd032f6dde30461749eb209db63 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-3.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-3.5_all.deb Size: 53260 MD5sum: 902e3bd5efad352888302149db7365b5 SHA1: 9299889054c494e642395da94e0d40deabeb6caf SHA256: c5516c02b3707f4b088e6a89f7b5772bf166c478e17e14ef144ff0d2ea78d0f1 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-3.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-3.5_all.deb Size: 33128 MD5sum: e58ac92412c00b94b68cc4cb848a91c9 SHA1: 961f5da33453d26f322f29b9ccf9cb26519701e7 SHA256: a1c5f745b350a495e8b30b7be9ff46af4cce643c4d0be6d9b679e64ea163ba8f Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-2.21 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 793 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-2.21_amd64.deb Size: 174752 MD5sum: b4c7324740e0131d5a31aefe182829ca SHA1: b8bbfab8b50e3c9296e516670461c1def757c601 SHA256: a86b9e3a18799c45486422ab9e54ea34a30dfe8b6e73e8f32346b3d1f33906c9 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-4.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 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-4.9) Filename: all/perl-module-build_0.423400-4.9_all.deb Size: 250900 MD5sum: 679c76be2c08e49dd2b3ef97365679ee SHA1: 6fdcde22d612a7d1f77071e89828bb71f0670781 SHA256: 134def38866b69f25de05fd27e371b564404373dd9576598bf38a071a6c0fb9b Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-3.4_all.deb Size: 29628 MD5sum: 1ca3b1ba13ee90b4ee9fa146dca273de SHA1: 0ce16578644b2bc6e4f39799b5a8f452b736d0fb SHA256: 109d9e2332eb596f50e7f5d5fb513b985aa81567c6ca9f3c539b9ebcfc7fe654 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-3.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-3.14_all.deb Size: 18428 MD5sum: 390a1ddc72dd129cefc77ff0142c2635 SHA1: 5f0e16cfe455aa9df75c84243f61d29ffc0a6caa SHA256: 68211217a4e60a680136ed92a00ddc5620f9790b9a7a985da7241ea960d141dc Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-3.4_all.deb Size: 17180 MD5sum: cd6bdda8aa11fdd154cb2fba454bbc2e SHA1: 41b6b5f2111a675d2c1a2771bf84398a3008e5c8 SHA256: 0bb972665a7329c758e606153f9d450379d3a3e75864085dfc0bf6f0e68631f7 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: 8836 MD5sum: b847470c0ac47dab12328f7df6ab7f91 SHA1: 09f061afd3bdfdd2dc5fe1abc5735f7328e8694f SHA256: 361089dc339b037f5d4d69e9c5c47352cc05110dbe097d8aa17c9c138541d0d3 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-3.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-3.6_all.deb Size: 15164 MD5sum: a9695cc8bec7286b9f1d3aac4f87f079 SHA1: 74211aa838fb9802acb38268f1fe1f2ff9aeb8f7 SHA256: 49a1497fdb9e809388e4ee2b33c504b71b2572f70503f4c21d558459388c98b3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-3.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-3.7_all.deb Size: 19036 MD5sum: f5b01f232d7de96fe8be8b416782febc SHA1: 9d56b1e84ef7709c7e082e2391744548aec62e6e SHA256: 235c0a3dbe9c24d7189f5876185df7ee05fcb3a569147c8321e9e78da5e27d33 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-2.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-2.13_all.deb Size: 22152 MD5sum: 93164c35aa9282e598e261a3e9722c91 SHA1: 92e497fc2a7037d4291fd3b533ab4c09d68e328d SHA256: eb7306c081dfdd667a7995c7330e4713d7f7862290aaa639fa32412a16b99444 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-3.19 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-3.19_all.deb Size: 56708 MD5sum: 257c45999aa532ece095629038e33e7a SHA1: 8282395a10f38eee008bd3675703a227086f5a02 SHA256: d6b9f1afad3f3e6b4f14163d9156c14425bfee3ac0d97be3103af26e9858c27e Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-3.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-3.9),libtest-compile-internal-perl (= 3.3.1-3.9) Filename: all/perl-test-compile_3.3.1-3.9_all.deb Size: 21396 MD5sum: 7cfaffebfcd9879ea132e7eed7328724 SHA1: 9e82d7b34c6d60d29dc04ab110ea57928070cec9 SHA256: bd12bcfc8e1dfa3754f0e2279645503e1b52371913e00ed6e81e1039bb3508e3 Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-4.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 352 Depends: perl Filename: all/perl-test-deep_1.204-4.7_all.deb Size: 81672 MD5sum: 1af0dce55120907b013467a6dbdb5831 SHA1: 592d19682e9b262b52831b4c7ee88247c61ab533 SHA256: b5aea88354c4d87ed8df8f7417754f7957bd1866f5ed87c5a21916ce24d72c2e Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-3.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-3.8) Filename: all/perl-test-differences_0.710.0-3.8_all.deb Size: 18348 MD5sum: 6211343ee4946d5a18264aab3d77e154 SHA1: c94a945bfa9003ec715e0f23c8736403ce380a85 SHA256: 60a89a20e4e94eaf9a02a3b91da7a1076215df1b8de3125a0f3bafc9fafcc8c8 Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-3.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-3.13) Filename: all/perl-test-exception_0.430000-3.13_all.deb Size: 18056 MD5sum: 3be6989dcf9ce59e39916ce057a2caa4 SHA1: 7661af829d6fa99980ac3082ef6ede35b6cd7367 SHA256: fb2b90a85316916c574bfdcfdac0a2bfa4319181acf6d916458426292c2dc577 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-3.18 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-3.18_all.deb Size: 23388 MD5sum: 0e3b5791ad5dc69762bce54010972255 SHA1: f48c1000bc31cb9d2470fbc0ec1166644df07caf SHA256: b5d4fb06ec8dc152b9ecd39a059d7426b858f9106e5e555d728ff21d5a5361be Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-3.4_all.deb Size: 13284 MD5sum: ee601ff2b1e8b8114918896ec3c406d8 SHA1: 3cdd83ee6ba6c1e0f4893226634cdc70cfe32bcb SHA256: 8ccb30c0462c3210d163b0731ebbe35a2372140e79617e5429bfc446e25604bc Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-3.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-3.9_all.deb Size: 10904 MD5sum: 138758c7a73ce364e3474083665c0250 SHA1: 5c12d2f43fb53136488c5a939e130412a10b9838 SHA256: 078d38d2d0418d271810700af24987b575c12bdcc184493c81bfac59c1aedea5 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-3.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-3.13_all.deb Size: 14812 MD5sum: 53f12699d53bb40b4426a2653d9733ab SHA1: 55b4666cf40456036c02628df7cc0849b0ddffdf SHA256: 774275c1088ceb2c5f42105f06ed7a5550062786b99daea6535bd35b9817a9aa Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-3.4_all.deb Size: 33256 MD5sum: 4211c64a59fef405e2b2bb1bc36c0831 SHA1: e3ec137d8c7d1499eab2cb1f8b8a47e300d25fc7 SHA256: c8a42559e914a039438a5af1ab39e3ca309b6de135a535d29b7615f82618670e Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-3.4_all.deb Size: 23948 MD5sum: 8fbf38f29ca95c1ec5daba1a3bd2cfd2 SHA1: 455c27d61b67c39347c4a08dcc552111f5df1e49 SHA256: ce67319b27a6c822e21b46d118dbf08b9dc58b54a5f39f4d033b115d8ec55469 Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-3.4_all.deb Size: 8888 MD5sum: b73ab6d452d74d9c4b2a171b51c157af SHA1: fd03265df949f0b9ea38a838eff894e94b12fd81 SHA256: 650b383326b827142fffcebea86ba9d5fe1541ca38e37f7a0397ad6691a7cefa 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.