Package: deb-perl-macros Version: 0.1-3.6 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-3.6_all.deb Size: 2782 MD5sum: 1faa9970696c91ae8d096df6ddac1c2a SHA1: 1546d1458656f05c5f593c1fbc61e502ba434542 SHA256: edef01c2ee66084fae1072067558841a4ca4c1f2d63b48368966e83c85f6b7f0 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.6 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.6_all.deb Size: 55564 MD5sum: cede0fa62b7648b3b0aabda15ce855aa SHA1: 7be64952fa7436fbe105c1e2a450e40255a1cd24 SHA256: 9c505465eddfa82612f9ae100d0e6c6b6721689087e22a4ba6e6e01392dede3a 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.6 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-3.6),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.6_all.deb Size: 8352 MD5sum: 8c8588d908cdd588036490f3d08d9545 SHA1: b3a0792b16ec760fbea585c9d02f3759353fcdd0 SHA256: 373af79bd28543bbaa80c0d68147dd6ad114e69b564896fc87d0e7ea9fb76250 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.6 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.6_all.deb Size: 26294 MD5sum: f3ef9e9a2278855668f7f1f00145e16c SHA1: 7417fa11b55e6ede8a4902feda606ff846cd6c9d SHA256: c5ba3cc6f91ba636f590752f7138d546d1ad4492830c700e68a2b0d18d246a84 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.6 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-2.6) Provides: lua51-libs (= 5.1.5-2.6),liblua5-1 (= 5.1.5-2.6) Filename: amd64/liblua5-1-5_5.1.5-2.6_amd64.deb Size: 347012 MD5sum: d715e49510f515efd7d5abfb5a2de110 SHA1: aecce87d78fddf97ee2e0c896d2cec79739e4bf1 SHA256: 069bdbb23c76f3a06a68f8a6b3d491ffe9032cd1eba4223996b3770ceea83938 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 1 Depends: pkg-config Filename: all/lua-macros_20210827-3.6_all.deb Size: 1528 MD5sum: 1caed5482f272374937af74af1cbd05b SHA1: f2e203433a17395d23eeb568107c80369d75f4a5 SHA256: ae1aac837f0296975a475d14e016b48b73f6099b5bffcf102d011c3d87e7ee60 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.6 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1487 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-2.6),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-2.6_amd64.deb Size: 426996 MD5sum: c6225d740284926c2255abb0493d984c SHA1: 735b3d4cdae2b3defa877e3908e4c7df706ee7a1 SHA256: a376864925e4ce0f751f6cc776973118f03d09248339038f3409c7e661060cc9 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.6 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1699 Depends: liblua5-1-5 (= 5.1.5-2.6),lua51 (= 5.1.5-2.6),lua-macros,dpkg Provides: lua-devel (= 5.1.5-2.6),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-2.6) Filename: amd64/lua51-devel_5.1.5-2.6_amd64.deb Size: 443114 MD5sum: fd71aaacaf27f6b49ce6870d6cd3740f SHA1: c851443cb42954c32157d978e926121c59bd6ae7 SHA256: b584bf7362e7ce4d7c9c0155bff447d89a736b355b48f735fe97fbedffc9887f 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-2.6_all.deb Size: 73488 MD5sum: 3343c97f941faedafc7ed4968fe26638 SHA1: 75bd07e1fa007d50de7744bd7e3250f49c87d7d5 SHA256: a46621e649adedbec2ee6e1c9d1ddc484856f10df126566e4170f0c491285af5 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-4.6_all.deb Size: 30214 MD5sum: 6efcfaf31e0d6b23fed7a76e42e93941 SHA1: c1631982c0dc67ebab7eeafe0c32441d349ec631 SHA256: d83c9c8b33c3540f195fe4efd98661714127cd18c7d25529ab6acaa69571e22c 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-4.6_all.deb Size: 22980 MD5sum: 508fdd1ff4bd6be4eb94605bddd548a0 SHA1: 79e22de4bf9c8e2e6a7c671612a6b906234aea1d SHA256: a8a9ba5b585d8e34b4bf513ca5da75f0c2de04744137fcd2457290d494a27d4a 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-4.6_all.deb Size: 6990 MD5sum: 08bbe630e9b4716e4ae7994c15634286 SHA1: 5a8babf286156b8af78140c24336c21cb5afb3e8 SHA256: 50b270ff15b63d72c9b2b33865e7a27a66a086904cf8794055edd8b9a0143c04 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-4.6_all.deb Size: 28326 MD5sum: c4e1a6b991edd6eefe052d0236a3582c SHA1: 89aebc493f1f7b631ab9e61f72635cfe27849236 SHA256: 5926260dd1f7c36b277c25765d53156731fb8fe8a6301ff7b27d8377bd247562 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-4.6_all.deb Size: 14520 MD5sum: e055a1a0cb1feec0a5aafb57417f5d15 SHA1: 44a8a0763e2f94473a83aed0b630f4004d9fc296 SHA256: 806e4540460583fb8e726cd45972102a6cd48aa2a9e3aaff7554bbd0494d0dd0 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-4.11_all.deb Size: 38956 MD5sum: da39922d94e2c0019b5e9a22818477b3 SHA1: fc6a70ae40a1e2f0048cad9bb17b2fa7a593def9 SHA256: 8a54ec84413c8025a6ca701cfdbab0b25617b975afb5cbabf3cac429237a39b1 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-3.11_all.deb Size: 39280 MD5sum: bb70fb801d3ab2241d185c3eb6ae04cb SHA1: 10e56f4f90650ccd5bcf1e28fdb5f451bc43ca4b SHA256: 49a3ca3ba86b3ef5fe2adadb63384592bab0ab45f29a11b71d95350636939f5e 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-6.3_all.deb Size: 298048 MD5sum: 08b0ce41cd427e3a5bede487a8cf24f9 SHA1: 95f572125e7b7d90df6844c8850382f8534a8637 SHA256: 29e19eeed58bfcce605d8cd82e54cae3a87e4ea31cb0bb8c97002d333f7fac8d 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-4.6) Filename: all/perl-extutils-pkgconfig_1.160000-4.6_all.deb Size: 10464 MD5sum: 893701dda0f7c0580352f802ee8a4444 SHA1: 19a69148979767119730ad3b407eed6f9cc89261 SHA256: 0d729d3e2114ba6c2c8cd659df5c95db2ab05f0464fad031612d3bcec0de64b7 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-4.6) Filename: all/perl-file-path_2.180000-4.6_all.deb Size: 30604 MD5sum: 176d9288b7178d26433f5a53fa9e887d SHA1: b483887bc51dbec5a8055e117ff2cef3eacee069 SHA256: a3aab63fd4405380ddc804f753cc038b1b0d537f6ea9b3d847fc7b51f8eba68b 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-4.6_all.deb Size: 53826 MD5sum: acc798c59927ca69c00891a930b61e68 SHA1: 43183b08b6d3bf58d321436ef9adfb921a4f0308 SHA256: 38847b9a5f4733bd4c0b6a6944b23ed12ca4601bb5f24fafc38ddd4b8b8d9947 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-4.6_all.deb Size: 33216 MD5sum: e2a169c1c21bca7b55c3242d3f4e5e41 SHA1: 6a76678b1eeadcba03fb9a59c0b5b3cf5166d9e6 SHA256: d303a9bbcdc014fb38f073826182b5641707d8b78f80cf955e142988dcf72166 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.13 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 719 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-4.13_amd64.deb Size: 216860 MD5sum: abe9fe74f10c4faef4820eb96a753d05 SHA1: c8a672b891b3faaf295b0921fa4d7493affd3cf6 SHA256: 5281f39407e44e4153d65832daf03b96c5837f5acf91bff3939897e63c6cb0ec 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.7 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.7) Filename: all/perl-module-build_0.423400-6.7_all.deb Size: 234382 MD5sum: de7f903e22409895b40cea4dcc56fb3b SHA1: aaf9765cff48d5fd917570a88a9a0e933b7a08f9 SHA256: 676b3abce467b64377a2482172d7d21a07fbf176f35770daa7f47a8bf77aa9f7 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-4.6_all.deb Size: 30062 MD5sum: 54780de42ae8b8bfe3d223ebf681221a SHA1: 6fae5355125a1d6fb412b438e0beecd06ea679cb SHA256: 8ab3da62f3783abaeb4bb17890deb4d0041939f3bf7e87f93bfb1d9eb3f8da27 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.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-4.10_all.deb Size: 17718 MD5sum: 88f95fe1992810b9bbacfb30cf84058d SHA1: c028fe08d6eb85cd75e27e011853f7df71c55179 SHA256: f85d5fc7bbc318fbe83a1a1d52d56e3d34c0ce3580d827cf6fb64d90848f860f 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-4.6_all.deb Size: 17492 MD5sum: 965ee7be429a1e4e66f149ab2183e532 SHA1: 9ea1842dc8c782802ab7709d7f173983161bdc3b SHA256: 8738b597137d04cbbf81e930f38130297240d23a117bdce96642ff11d2d688eb 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-2.6_all.deb Size: 8744 MD5sum: 6d999c0164c5e5ec004453a4820864f7 SHA1: f5d883882ce525a301e6b42f63e4c5cbb00d6d2f SHA256: 2d564e70b82a791e5d08ab41299960322ac03faea312ee2380bcecdc48a77d0a 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-4.6_all.deb Size: 15484 MD5sum: afe54fdc37f7d85f26916f8c9592bba2 SHA1: e570d196e7de6e5c4c833e5bb2473cb49f351c56 SHA256: 1b0be46527a9fd3c37d913e4ff5140542d0e6cd307992dda29202d38a1a1be47 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.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-4.10_all.deb Size: 18490 MD5sum: a6588dddf8412b5aa8e7e2b20106a052 SHA1: b9a2fcd6be9a7e3ec55033e41b7f871c1e8f8899 SHA256: 2c6f9652e7c570a02fb06d565a1cc99a02eef01294fb20854767a7e8982f8276 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.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-3.9_all.deb Size: 22442 MD5sum: 6a214d2e911c8701634615eb17d91e0d SHA1: a080d34716ea83ee2a62e98b8f0a8c5ff936b53e SHA256: 47292e855fac84239b6b018a28c634b2f1e28f35435e2c3c10b0d6d510149f92 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.13 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.13_all.deb Size: 56430 MD5sum: a65718c0517db178d71f7ed705d98cb6 SHA1: 2f9b88658ba468289e145571bfab5b72d511dcc6 SHA256: 47a741a583a04a87f32f110275c269122e3b5be561ceca6e6d2a0e365ffcd1cd 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-4.7),libtest-compile-internal-perl (= 3.3.1-4.7) Filename: all/perl-test-compile_3.3.1-4.7_all.deb Size: 20040 MD5sum: 0ae65d13b31edc44dc16ad81e5488a1e SHA1: f4952d10bb01b12f822629e0a4ec03c571804779 SHA256: 4db10caf2d9950afd5defb22d9b38e8a5027de0c4923e1532f847958cca22a90 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-5.4_all.deb Size: 88606 MD5sum: 695d4f7aaed7ecefe57d682c1091ea2c SHA1: 6362c06e367d7866efe29fbd8c47ab918cb10767 SHA256: b3f270d322cfa5e846594bca4a962aed32df7f904bf51d3e038504efeae7273a 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-4.11) Filename: all/perl-test-differences_0.710.0-4.11_all.deb Size: 18548 MD5sum: e3a25620e75996bfc1a2a4cb30ad31a7 SHA1: 2d4667897d6be5dcd0fdd9a6839b2ebd7a673242 SHA256: f0939f306eb88f68f72b53743d46fd7a6b1f27e1d1328a025ff794945366717f 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.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-4.11) Filename: all/perl-test-exception_0.430000-4.11_all.deb Size: 18228 MD5sum: d672b7a9ca35501ab25d0914cf3e74f3 SHA1: c5538d36feff5e31975a1a736b4efe4a040edd6b SHA256: 98502155ae16a5de6dfdacfbd5a989b024833857fa805776be3ac1482b124797 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.13 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.13_all.deb Size: 23414 MD5sum: 50b684a6c48e1d0fa2eca86b7bc3d770 SHA1: b2ddd642c88da2be263ef425e46b9e61306cdc09 SHA256: 9a84eda91ae44b0d24980fd148aa749ac68982be26624ba5989db7ef24609852 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-4.6_all.deb Size: 13382 MD5sum: 21e97b01d76b95567f041b531b05675c SHA1: ca70820f64d1dc9965150a8f88410cb69e114052 SHA256: 1c54aa1b51149dc2b945018aa68a6353ac334b88791cccff380645f0bc905a40 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.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-4.14_all.deb Size: 10808 MD5sum: 10ad1ae93dc02c583cee3bb5cfc31732 SHA1: a96109b4cc547901f9deed2e6f05ea8a8a85927c SHA256: d602db0700f2a4d9671b78e74e970d9b5f9d58ff4d249071778a8ecc15b51515 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.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-4.10_all.deb Size: 14824 MD5sum: 0083afb7421432cc34f56b413cbd40b7 SHA1: ec290dd0e852a7b5d7eb61ae333881efc7336319 SHA256: a94bff787bbe1a30b4e616d96cb608b9086ea36208f52b64c1adedbeee4922c4 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-4.6_all.deb Size: 32916 MD5sum: 2b946b9889ac3d6a87736d4ca634feef SHA1: ed0b22d6913333adde5e3502c4f1c85eb1e7e566 SHA256: 5c599fb223b2a1cd58732f271a3e3d1c02cd779f70b7384bf577c17ff2a66ae6 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-4.6_all.deb Size: 24314 MD5sum: 8e6be1cafc74496d94c8b0c68c1afd5a SHA1: 4d0998f65544478741cd2b05b5ef219c229be8ec SHA256: dc092284c2e3912f2fb1f45234faed3c03a42c7f0f6190c59dcd15e9fc70d6fc 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-4.6_all.deb Size: 8698 MD5sum: 69ce103814cecb52cf1d4e97b3d84ad1 SHA1: c42054e39861e3d9841c60afc29141413bea1c2b SHA256: 9fc594bcde88788545a48e896aaf36e10545e13ca1df17c09a5020fd7b7208b9 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.