Package: deb-perl-macros Version: 0.1-26.5 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-26.5_all.deb Size: 2564 MD5sum: e0351161d855ec418fe5a45c5e921a31 SHA1: 4411ae1f56f2f93144d506a47e0936614955af66 SHA256: 7085ebe3c653e1537a6368e8f8e0258946193e0e9e8e438ae3d2a624eedc2092 Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-39.1 Architecture: all Maintainer: debbuild developers Installed-Size: 209 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_24.12.0-39.1_all.deb Size: 56034 MD5sum: c9cd1b472986028a2a8a65b7ffc18192 SHA1: 85f370ff34ca464ffe7e07569d1cea6177285414 SHA256: 980d5abcdc998f2932d846ee83960e11c26994f187f260c02caab32a4040fba4 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-39.1 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 24.12.0-39.1),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-39.1_all.deb Size: 8346 MD5sum: 116a42d7c2b6a51409a4baead16af959 SHA1: 91ac33844927daf95a93a885d031aa018535abfb SHA256: 3bd4961d8977a8c130d6cecff1ebc4e3798889be2a9091bcd3896fe8e6004a57 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.7-17.1 Architecture: all Maintainer: debbuild developers Installed-Size: 126 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.7-17.1_all.deb Size: 26274 MD5sum: 8183f5513d3ca0c6d1ec1375da2eae05 SHA1: 7e8edea471628420c58d4ac7dc7c0b0bd187b2a3 SHA256: 043debd9c89ce9219c7899740ef6b4139fd2ea4172a75c28107be5d212ff8178 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 881 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.4) Provides: lua51-libs (= 5.1.5-71.4),liblua5-1 (= 5.1.5-71.4) Filename: amd64/liblua5-1-5_5.1.5-71.4_amd64.deb Size: 352540 MD5sum: 9fa5f18917ac71fc598c50ec2708d605 SHA1: 11f7af84e6dbfbcff94ef0d506400cbd1244bf71 SHA256: 448f61a6a58ee9b1037169fd0246ee0becc1772189c38002de10cfb4659f0667 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-36.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 25 Filename: all/lua-macros_20210827-36.1_all.deb Size: 1330 MD5sum: fcf27bea87b0300decfbe77215e50a7f SHA1: 79005306f814e5e4bf6160b7733e9787899b3312 SHA256: 45c03a371bcc933380b062dd62b60001d0c573df541175b2a03abf91ef8b3455 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1527 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-71.4),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-71.4_amd64.deb Size: 434164 MD5sum: 69a383c57150d2dd0ff0dc55fa4d5b12 SHA1: f65267524cae89f0eb25429146bb1773829bb9b9 SHA256: d86aa74dce67d552c67f438a36e0a913ca60adf47d5deb613fdcf083f96bc4ff Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-71.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1736 Depends: liblua5-1-5 (= 5.1.5-71.4),lua51 (= 5.1.5-71.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.4) Filename: amd64/lua51-devel_5.1.5-71.4_amd64.deb Size: 450342 MD5sum: f66998ead5290cd9caa756483c9884ad SHA1: d1d1575f416511ef1ad6e6cbdfe2e9f3501d9962 SHA256: 9d56e371b9c1776027c53a6493583e595601db5bf715e024b5729e7fa7505729 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-71.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-71.4_all.deb Size: 73728 MD5sum: bb9b88ccf200b8b3673d1605515b52db SHA1: bee9276fe81396446838b7ac8ddb5ef29d392b8d SHA256: 675274d06c0f1e5b53d8083d8d8a0c31bdb84a475c013734ab913d6b821d178e Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-26.4_all.deb Size: 31278 MD5sum: c246e0183e35a3e043650fe7ffb2b0f0 SHA1: 3e270ff63a8bede7a5420d1202e015604cba0071 SHA256: 6232e523b4dd55c1eabbe2df17a34dacb6ae6156cd1e5216d30594392874cafb Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-26.4_all.deb Size: 23276 MD5sum: 89de55aea8b41aa53a9c0bdaf19209cc SHA1: 0cfee0bea987cae495362365247414c70e9bc19e SHA256: 8e4a139cb1fcc33f4300747e8e12a4b59c950a42f90fe71c85ca4810f90b00b3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-26.4_all.deb Size: 7262 MD5sum: cb316acb7fcdfefec8c092db22f87b12 SHA1: 4e15407878b59f60470d2d84aff329502d3bb477 SHA256: fb36a4e7e2115bc5ef1f482f1c283280cc2bb8fb4c275bf2b0086ca4a105cae1 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-26.4_all.deb Size: 29400 MD5sum: 11a63c12778ce33728ea02880e46fec7 SHA1: cf1c11ebbed7399caf7fb0e402051d9bf8875cfb SHA256: 940259dd22478a074e04a1722575b25ff4b194a4f824b18f93b304bb3788569f Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-26.4_all.deb Size: 14790 MD5sum: 19f2fe95817b6e4e0a7178d90deef2c6 SHA1: b4142db744388893cdd0b20b3fd95856be7b27e4 SHA256: 998841ca9066304f11aecd16f21c1a97c883987522357638fcdfa7ab0fda2ecd Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-26.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-26.8_all.deb Size: 40404 MD5sum: e2da6854e5312e70aacfabb2c1488eb6 SHA1: af9b0db51fed75b4a405c0a9005f75ece538abbd SHA256: f573db5d597d7dc28768f422f507e3b947dcafb30633c22a3a5419cd79a34a77 Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-25.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-25.11_all.deb Size: 40748 MD5sum: 70048ee60c5c465c82dd2e613f18a379 SHA1: feaa76edb5ec35e954bb1eade79309d0c5236c67 SHA256: 045fa0c3c20037ebe2394ca020cf3e593544fde765ced0638b5333ab070a9373 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-11.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-11.5_all.deb Size: 308282 MD5sum: c1794c6ae9d7ca01839790931f60d832 SHA1: e7ec2d211bbcabe8679f94a4e5ed089d6efbbccf SHA256: 745ea6522ecc2f2dcbe5fa27b1a6dbb512b006e604a35b86087d8821ab55db68 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-26.4) Filename: all/perl-extutils-pkgconfig_1.160000-26.4_all.deb Size: 10802 MD5sum: 1ceb8afaaab3d18f4136d432dbd128c9 SHA1: 86aab66402095a9dfe600020d9d03c327a88b4c3 SHA256: b2941c32b898b8599e94c7c21b977e69759c79ee09c2b192533738f10ac1f4f9 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-26.4) Filename: all/perl-file-path_2.180000-26.4_all.deb Size: 31564 MD5sum: df2c3a2b9e8c9ed1e755f090f5dccf63 SHA1: 320bd0822add835a72960231a17b81ccbec05112 SHA256: 2c4d37e42fce4857ad0832e9e07b0e449f3399cd163494633a2cf31f11c9de3e Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-26.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-26.6_all.deb Size: 55348 MD5sum: 6978c0bbb75cade0d9f30190e1b755a8 SHA1: de15fa6c0bc086da48501efc4d5d560f1db37f0d SHA256: eede9d3b31860826c94afb780c1c6ac598bb7f9ae1dad33b3be35380dd1b9202 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-26.4_all.deb Size: 34260 MD5sum: 0b27086d33e911fbd1c1ef5e60035753 SHA1: 5194958c173ef604bc2a40c9e17b335ed2ac8b86 SHA256: 14ba267de99e173be86523c51a68ef5068d158408a3b21eaa696deeaafbc8caf Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-27.31 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 753 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-27.31_amd64.deb Size: 205848 MD5sum: 88a94d28d168cf499e27c1d2c7e8f797 SHA1: 2c3a6494d53080d74aa14640522386ef8f7d5098 SHA256: f6c6eb71322f27cff9c63785b87db0f046e364e7f018b58d54152ffe7bb3b17c Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-29.11 Architecture: all Maintainer: Uyuni packagers Installed-Size: 733 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423400-29.11) Filename: all/perl-module-build_0.423400-29.11_all.deb Size: 255470 MD5sum: 3c95f827ac47fa4ab2d7e2132ce2acd4 SHA1: f94db4b38b80803aacde36e84a44a7929b826261 SHA256: 08ab8e211df34b3701547b3aa9bb4d207a88a18d7e6c690f5fe341b7dfa33340 Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-26.4_all.deb Size: 30768 MD5sum: d280d73ba6c28198360257d746093bb6 SHA1: f30fd2774527a8d5e3505ef24eb5bec9eb46e4ed SHA256: cdb5241ef3b05e8b6ad8cb0df7ad1148a45569900b16ef5b88e94344aeec72e6 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-26.15 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-26.15_all.deb Size: 18748 MD5sum: 9003c03b569cd105fe5d494c256281ec SHA1: fc0f127eb084be973d88238c428c85371111d6b1 SHA256: 130a6d9f2fdaee3e21dfbdd5d9697852181590dc8b083a240ba871bd0ae46edf Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-26.4_all.deb Size: 17788 MD5sum: b0fe755bac1d5c3bc58ecac725be35a3 SHA1: c2b2e48b44c7ba9ba574ea1f732257c0cd0dd0d7 SHA256: 2609936c5b942de337ff1a9ab9f5039a8e930050c608217b707115cb7777bbbe 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: 9002 MD5sum: f7c828a28cbed5d5f686bcbf1c13f9f9 SHA1: 6c55fab570d8fc5881114f2a464414b6ae638a29 SHA256: d3bcc085faf5ab35f715848acbb01252113767f918623d97349eb5ba8bf2b286 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-26.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-26.5_all.deb Size: 15754 MD5sum: 9c021c542f2257added6d1d2a81eba70 SHA1: 7cccbb783369c0aa7c4ef9cbda30a62cb49603a6 SHA256: 3f76fc47921459345eac8d3b070acf6e933262e717669ad77774d8fc9569fdb7 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-28.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-28.6_all.deb Size: 19394 MD5sum: 9b80816d06d36d12cb617ff30f91a957 SHA1: d13355c3b3503ed2a9b178c338c6a0dbe4beffe1 SHA256: 74558b4ec2cdf1da508624175da2a072c8c84c0bb14b90a14d3bb647c48e95db Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-25.17 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-25.17_all.deb Size: 23046 MD5sum: c55a824755efe9552f760c811683c7a2 SHA1: 4b15e2c1b089fe0c33157d6ef500c5b344da5cbe SHA256: 8e662670a371545bab064a4450421d25cd3d59f94ad537c4e3981604389647b2 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-26.23 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-26.23_all.deb Size: 58410 MD5sum: a8678387a7488471313660bb774423a8 SHA1: 4be5f206ab1da66906f91f20348663749c70bbb0 SHA256: 4ad308e5e44f26e5f92927427dd94a25f9792cb08b72ff53d3d5198d02f610c9 Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-26.14 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-26.14),libtest-compile-internal-perl (= 3.3.1-26.14) Filename: all/perl-test-compile_3.3.1-26.14_all.deb Size: 21982 MD5sum: b73d6af8c70f25f72c416413d4554d06 SHA1: dea61ecdb6cc156fe39318b3852b5137f11374c5 SHA256: b8b5329a8d5a14ea0097cac6c2d9df1df19d320193af2ebdf97b0464f0a14573 Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-27.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-27.6_all.deb Size: 97424 MD5sum: 52a7efabe057c3c689940165e821d363 SHA1: cb21f206f346104aba9d84576cf8faabf4c49da0 SHA256: 1d4325108fbecbab7a0c23872a626c56cc05935dfc93bd1a4dbe8b11db3753af Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-26.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-26.8) Filename: all/perl-test-differences_0.710.0-26.8_all.deb Size: 18872 MD5sum: d7420322b54ca70b80495c3a0be79390 SHA1: 8ce042107cba893b8cd4bfdd516935811b0651e1 SHA256: be50f954ed32b3fb9cd6514dc53c72987aba8aea40f12afa32d5719cd8cf4dfa Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-26.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-26.16) Filename: all/perl-test-exception_0.430000-26.16_all.deb Size: 18484 MD5sum: 757e134fa93fb3bef9b04a1d35169715 SHA1: 2b72d0d2089b0c5b92bd694c57ef37def37aa998 SHA256: 70e6671271db65b01009c2cf066b26938bb6eda1845f1423d54287ab75ffb2cf Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-26.23 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-26.23_all.deb Size: 23942 MD5sum: 16d751f8961ddfadca7248e6413621d9 SHA1: dbb91c4c5826219bcd7df548c7fe7a32d92bd9c7 SHA256: 39b7c526b3531e76d7d9f251dcc0df319df0e6794747b3067a6f477388cfeae5 Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-26.4_all.deb Size: 13662 MD5sum: 4936019bba23a6d8889bb2a16fbd34aa SHA1: 68d37b9f73380e466653275d8b8c1ddad9874ac5 SHA256: b2cf6182e006b5d83da46be756134005b218dac5b408584053fef7fbfac22d7f Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-27.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-27.6_all.deb Size: 11068 MD5sum: 01ee10ffd824b30603489fdd4ce3fe5b SHA1: c1b7c8c2112c2d9c67c74afbc25c2b9945632a9b SHA256: ca402674b7b542a4fc9d762264a522e0048c9f35fdfb9fbde10c897dfa683db7 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-26.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-26.16_all.deb Size: 15130 MD5sum: 634dde38b5f2cbe496e77a92f83dfff4 SHA1: c5c3c951c7496edbe65561516970330402a46e30 SHA256: 293a2be97602748bcb16f018630889970eeabb23bd808805d12c72c80195f1d3 Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-26.4_all.deb Size: 34640 MD5sum: 04ada83f66c6a56d9f230b74a10a3ec5 SHA1: efd57c17bd8ed44cff4e31e9d247a26468a8d548 SHA256: 3da60097e0e96964bb2a42d9b7b079a82c7b60520145c167ff1e126ed35047b3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-26.4_all.deb Size: 24570 MD5sum: 7f5072b53ad24b556ca59a984a2b82fe SHA1: 7acb8874870f32ed85d7b9f2ced74fed1c17e464 SHA256: 0abccf6b812976ff73e20758014cc50a0da5fb07a9a3e133b294ea230b65a0eb Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-26.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-26.4_all.deb Size: 8968 MD5sum: 50cac39b16a57b188ef5812ef4a9fec3 SHA1: 1ba5b741a562c33a5a68c6060c6827829f7c664e SHA256: 490669d382e2b54c7e2880575ae206e2d4b96501a64be812b7f52bf64537f880 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.