Package: deb-perl-macros Version: 0.1-2.4 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-2.4_all.deb Size: 2576 MD5sum: 7a9c53c4c58be647f380a169e8c6dfa2 SHA1: 33882ee04398e3fc0e902d340ee37632b2eb187a SHA256: b245cac5c259722a84802e46a507f74a6d506e400cb97e42bbe06a4c1f7061fb Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-3.1 Architecture: all Maintainer: debbuild developers Installed-Size: 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.1_all.deb Size: 55564 MD5sum: de718a31408b017dc551df4818b04798 SHA1: f4f3ff9a38d0e936ad3710aa7c54dc11c0619a91 SHA256: 5f88b9b9585bc0cacc1c05760a0e1dc0cfbcd049ef00b90663a57f57b6a0740a Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-3.1 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-3.1),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-3.1_all.deb Size: 8352 MD5sum: 92bccd4eb356e125ab34b3a6ee285ddb SHA1: ddf68ba71ad2751e147195b4983f048c088771b3 SHA256: d794a606deb5945456ac73f2dc15d0cfab7360ecc2bfed9df50e5b3e5507a7b7 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.7-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 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.7-2.1_all.deb Size: 26180 MD5sum: 88d25b9a057de83928975b59a8310f8c SHA1: cb47444b597f09aaeb43fe91716f2e708da205f1 SHA256: 4c964cf28cc399754eeb0f81e47ace438a8bda2b7aaf48aff5a1e85f48dd367a Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-45.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 854 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.4) Provides: lua51-libs (= 5.1.5-45.4),liblua5-1 (= 5.1.5-45.4) Filename: amd64/liblua5-1-5_5.1.5-45.4_amd64.deb Size: 346894 MD5sum: a02d0540524295746db756ea4064c14d SHA1: ab93594849ddf73c67a32f05b4fee885f1e90ced SHA256: 19f4a6d350144c0c279e5538a25d76f07fa264ced4112a9824c137c6984b65dc Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-28.1 Architecture: all Installed-Size: 1 Filename: all/lua-macros_20210827-28.1_all.deb Size: 1332 MD5sum: e33d71e35902471617dcb3917adc7825 SHA1: 28094a964d3ef8f8a9d7989509d2d71ba4b3c154 SHA256: 5ff4ed7f611a5a38b8de7c987f76e7f5bb8e866631ef842bd344da33464b61c4 Section: Development/Languages/Other Priority: optional Homepage: https://www.lua.org Description: Macros for lua language RPM macros for lua packaging Package: lua51 Version: 5.1.5-45.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1476 Depends: dpkg,libc6,libreadline8t64,libtinfo6 Provides: lua (= 5.1.5-45.4),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-45.4_amd64.deb Size: 427806 MD5sum: 294fcd55c314c9789a9052c528e1fdfa SHA1: 0610915467ee2af635ce1c1f731bb0e0f5a59605 SHA256: 5293d15d44f85f65d52ff11091e778e2d65aa2135da9676619a40faa8c967934 Section: Development/Languages/Other Priority: optional Homepage: http://www.lua.org Description: Small Embeddable Language with Procedural Syntax Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua51-devel Version: 5.1.5-45.4 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1693 Depends: liblua5-1-5 (= 5.1.5-45.4),lua51 (= 5.1.5-45.4),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.4),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.4) Filename: amd64/lua51-devel_5.1.5-45.4_amd64.deb Size: 442938 MD5sum: b5c21ffea346a285f1848e204885f177 SHA1: 18b5f3994d2aa59d0d033b5b975803460128106e SHA256: 2ff77ff5a46cee6985a8c895e3e908717031df5dd48fa267159b1619e0423ca0 Section: Development/Libraries/C and C++ Priority: optional Homepage: http://www.lua.org Description: Development files for lua Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . This package contains files needed for embedding lua into your application. Package: lua51-doc Version: 5.1.5-45.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-45.4_all.deb Size: 73396 MD5sum: c43635984626ba05a3839c603e2eb016 SHA1: f261961a666db9094c1b31ba74bb5728ce49c446 SHA256: 9495f76d0d1440092dff6ffcb46eb448b3dce522062f8c04b87e697521108129 Section: Documentation/HTML Priority: optional Homepage: http://www.lua.org Description: Documentation for Lua, a small embeddable language Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: perl-capture-tiny Version: 0.48-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-3.4_all.deb Size: 30204 MD5sum: 51dc964f3d444692bbb49e92eb1d381f SHA1: 9b9cfdb0df6ce32fb5587d52d4f1eb7e2c8fb5b3 SHA256: 9db0812bba102e6a18330da1fa9112cae13806ed5572f919abb23140579cd38a Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Capture-Tiny/ Description: Capture STDOUT and STDERR from Perl, XS or external programs Capture::Tiny provides a simple, portable way to capture almost anything sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS code or from an external program. Optionally, output can be teed so that it is captured while being passed through to the original filehandles. Yes, it even works on Windows (usually). Stop guessing which of a dozen capturing modules to use in any particular situation and just use this one. Package: perl-carp Version: 1.50-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-3.4_all.deb Size: 22974 MD5sum: 8cbfbad07df336d6fa95205c25b4c89e SHA1: e59a0a0a5fcb0c1092df2465262149b971b0b74e SHA256: 96d9abb313b9a6d72c24a192d8e3524852cedaf66bb412672f37c5c41d84a69a Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-3.4_all.deb Size: 7004 MD5sum: 7dea241aab57b7ff66fa6c67fd546ec3 SHA1: 7f9d1a5382fd5647977322362b2392da82e2c00d SHA256: 385697bcac76950204c40a09030720c75b19757e2c3552638043fffeaab56b5e Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-3.4_all.deb Size: 28322 MD5sum: d5d4a3b2820b096cd1235be7f1564891 SHA1: b9fb4257e6419a9fee1ae1494ca8e2747c05ad52 SHA256: a6640611d19616c97498c27120735cf74298c04a11d121e98e3f3a2ea8a85515 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Devel-StackTrace Description: An object representing a stack trace The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace' and Devel::StackTrace::Frame. These objects encapsulate the information that can retrieved via Perl's 'caller' function, as well as providing a simple interface to this data. . The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame' objects, one for each level of the stack. The frames contain all the data available from 'caller'. . This code was created to support my Exception::Class::Base class (part of Exception::Class) but may be useful in other contexts. Package: perl-devel-symdump Version: 2.18-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-3.4_all.deb Size: 14512 MD5sum: 575f5e826d25dc5aeeb2c9d33f2be8d0 SHA1: 329ff39e193b3feb9800aeef1426d4a8702a7ba9 SHA256: f6160ceb6c04bddfd5ddb2a03d2972f0664d28e929d8be123cad6dabab1856f1 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-3.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-3.7_all.deb Size: 38956 MD5sum: c53a9b5f23d5faa000866bb02366e373 SHA1: 2589939c117694cda386727b69b7c0791fa1b559 SHA256: 4a53a763c1b15ef769c0450092d353607c0ea35047dadfc380df4bf3999f79db Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-2.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-2.7_all.deb Size: 39272 MD5sum: 37dbca59cb66374a1641639f1be15bde SHA1: 8b7855b15296ae994905e5011a41274f50855d77 SHA256: d54b4361a4e77be79c2944ee030119b5183d54122f501feaaf63d0ae100ab972 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-CBuilder Description: Compile and link C code for Perl modules This module can build the C portions of Perl modules by invoking the appropriate compilers and linkers in a cross-platform manner. It was motivated by the 'Module::Build' project, but may be useful for other purposes as well. However, it is _not_ intended as a general cross-platform interface to all your C building needs. That would have been a much more ambitious goal! Package: perl-extutils-makemaker Version: 7.66-4.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-4.4_all.deb Size: 298298 MD5sum: b283d9f73de5dc1371a8f979daaaf7e9 SHA1: 3ed2654088c67c6e18fd05d0c0ee2044452efae9 SHA256: c531296f99c09362db850e9a2fdd8380138652a650efc3bd46232e93cb94b5b7 Priority: optional Homepage: https://metacpan.org/release/ExtUtils-MakeMaker Description: Create a module Makefile This utility is designed to write a Makefile for an extension module from a Makefile.PL. It is based on the Makefile.SH model provided by Andy Dougherty and the perl5-porters. . It splits the task of generating the Makefile into several subroutines that can be individually overridden. Each subroutine returns the text it wishes to have written to the Makefile. . As there are various Make programs with incompatible syntax, which use operating system shells, again with incompatible syntax, it is important for users of this module to know which flavour of Make a Makefile has been written for so they'll use the correct one and won't have to face the possibly bewildering errors resulting from using the wrong one. . On POSIX systems, that program will likely be GNU Make; on Microsoft Windows, it will be either Microsoft NMake, DMake or GNU Make. See the section on the L parameter for details. . ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the current directory that contains a Makefile.PL is treated as a separate object. This makes it possible to write an unlimited number of Makefiles with a single invocation of WriteMakefile(). . All inputs to WriteMakefile are Unicode characters, not just octets. EUMM seeks to handle all of these correctly. It is currently still not possible to portably use Unicode characters in module names, because this requires Perl to handle Unicode filenames, which is not yet the case on Windows. . See L for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-3.4) Filename: all/perl-extutils-pkgconfig_1.160000-3.4_all.deb Size: 10466 MD5sum: 780fe58599a07bcb270d5cda645ee003 SHA1: 820e6b51cb975d8d7ef68529408fbd6c2a7f5455 SHA256: 84d86a650cbe203d48e8a3919012b3ebcb26143e63276f20530d4b6fb27bc890 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/ Description: Simplistic Interface to Pkg-Config The pkg-config program retrieves information about installed libraries, usually for the purposes of compiling against and linking to them. . ExtUtils::PkgConfig is a very simplistic interface to this utility, intended for use in the Makefile.PL of perl extensions which bind libraries that pkg-config knows. It is really just boilerplate code that you would've written yourself. Package: perl-file-path Version: 2.180000-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-3.4) Filename: all/perl-file-path_2.180000-3.4_all.deb Size: 30594 MD5sum: 53387584a67a3bff56b9ad2146f2dafb SHA1: 83f7e9b69a9bfab18bae3775bb038375d907c40b SHA256: f36acbef18b65464618eef5da635460c15e01c22269de8a57f34ee5a894da926 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Path Description: Create or remove directory trees This module provides a convenient way to create directories of arbitrary depth and to delete an entire directory subtree from the filesystem. Package: perl-file-temp Version: 0.2311-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-3.4_all.deb Size: 53810 MD5sum: e08a5220a5356720f9255ac43dee2266 SHA1: b868b9ebed5419cdb0abc772139112d5a881a327 SHA256: 303537599f310aad99750fb50937f9698419fa45af14cdf66a16de1616172e6d Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/File-Temp Description: Return name and handle of a temporary file safely 'File::Temp' can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. . The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See "safe_level" for more information. . For compatibility with popular C library functions, Perl implementations of the mkstemp() family of functions are provided. These are, mkstemp(), mkstemps(), mkdtemp() and mktemp(). . Additionally, implementations of the standard POSIX tmpnam() and tmpfile() functions are provided if required. . Implementations of mktemp(), tmpnam(), and tempnam() are provided, but should be used with caution since they return only a filename that was valid when function was called, so cannot guarantee that the file will not exist by the time the caller opens the filename. . Filehandles returned by these functions support the seekable methods. Package: perl-ipc-cmd Version: 1.04-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-3.4_all.deb Size: 33228 MD5sum: 296636395d40a88ac9d2c0748afc595e SHA1: c62cc091ce29814be3c72afd8299c361f623d47c SHA256: 95cf1238e6bcefa1f5a8484dbc93fa08f25bdecbd24a39833e68789d9fcc7e1d Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/IPC-Cmd Description: Finding and running system commands made easy IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. . The 'can_run' function can tell you if a certain binary is installed and if so where, whereas the 'run' function can actually execute any of the commands you give it and give you a clear return value, as well as adhere to your verbosity settings. Package: perl-lua-api Version: 0.04-2.19 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 709 Depends: perl-base,liblua5-1-5,libc6 Filename: amd64/perl-lua-api_0.04-2.19_amd64.deb Size: 215080 MD5sum: d180ee1fa5a899a226ba12f33ed4ece6 SHA1: 42d0dbdaad079926c4aa8b5874546322dce22a7b SHA256: f30f115ac223f133a77c120bb7fbc356c18652b31591fe2859d1fd86e54e4b79 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Lua-API Description: Interface to Lua's embedding API *Lua* is a simple, expressive, extension programming language that is easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based embedding API. It allows Perl routines to be called from Lua as if they were written in C, and allows Perl routines to directly manipulate the Lua interpreter and its environment. It presents a very low-level interface (essentially equivalent to the C interface), so is aimed at developers who need that sort of access. . *Lua::API* is not the first place to turn to if you need a simple, more Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher level approach and masks most of the underlying complexity in communicating between Lua and Perl. Unfortunately by hiding the complexity, this approach also prevents full operability. For *Inline::Lua* this is a necessary tradeoff, but it does mean that you cannot create as tight an integration with Lua. Package: perl-module-build Version: 0.423400-4.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 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-4.9) Filename: all/perl-module-build_0.423400-4.9_all.deb Size: 234942 MD5sum: 97b6f451254d57c97e6242d2947ac18e SHA1: 2fc71de91caae69b083d8f3d17a9e150970d3a90 SHA256: d2d1dc11001ead21b511fea0175c93bb9ed7add180b2fb252f6ebc5ce53fbb9d Priority: optional Homepage: https://metacpan.org/release/Module-Build Description: Build and install Perl modules 'Module::Build' is a system for building, testing, and installing Perl modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'. Developers may alter the behavior of the module through subclassing. It also does not require a 'make' on your system - most of the 'Module::Build' code is pure-perl and written in a very cross-platform way. . See "COMPARISON" for more comparisons between 'Module::Build' and other installer tools. . To install 'Module::Build', and any other module that uses 'Module::Build' for its installation process, do the following: . perl Build.PL # 'Build.PL' script creates the 'Build' script ./Build # Need ./ to ensure we're using this "Build" script ./Build test # and not another one that happens to be in the PATH ./Build install . This illustrates initial configuration and the running of three 'actions'. In this case the actions run are 'build' (the default action), 'test', and 'install'. Other actions defined so far include: . build manifest clean manifest_skip code manpages config_data pardist diff ppd dist ppmdist distcheck prereq_data distclean prereq_report distdir pure_install distinstall realclean distmeta retest distsign skipcheck disttest test docs testall fakeinstall testcover help testdb html testpod install testpodcoverage installdeps versioninstall . You can run the 'help' action for a complete list of actions. Package: perl-module-metadata Version: 1.000038-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-3.4_all.deb Size: 30068 MD5sum: f07ece4619d82903eb41c58da137e3fe SHA1: de068409b054c33b25a7a8054be563b6a7a4d959 SHA256: 3036cd851361dfa215c550808b72e69ae192e26d9e14e2db0b665b19b2f21940 Priority: optional Homepage: https://metacpan.org/release/Module-Metadata Description: Gather package and POD information from perl module files This module provides a standard way to gather metadata about a .pm file through (mostly) static analysis and (some) code execution. When determining the version of a module, the '$VERSION' assignment is 'eval'ed, as is traditional in the CPAN toolchain. Package: perl-module-runtime Version: 0.016-3.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-3.13_all.deb Size: 17720 MD5sum: 741e2a1bd8c24ae65af906f400dcfede SHA1: 0ee1c87fc299db5b257574d2524e44fb7d1ecce6 SHA256: a1a9dda8616040ab99d224ba8a3c3c0804c078e3827a6d8f48b3ad2ae479a6f2 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Module-Runtime/ Description: Runtime Module Handling The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure. . The parts of this module that work with module names apply the same syntax that is used for barewords in Perl source. In principle this syntax can vary between versions of Perl, and this module applies the syntax of the Perl on which it is running. In practice the usable syntax hasn't changed yet. There's some intent for Unicode module names to be supported in the future, but this hasn't yet amounted to any consistent facility. . The functions of this module whose purpose is to load modules include workarounds for three old Perl core bugs regarding 'require'. These workarounds are applied on any Perl version where the bugs exist, except for a case where one of the bugs cannot be adequately worked around in pure Perl. Package: perl-mro-compat Version: 0.15-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-3.4_all.deb Size: 17524 MD5sum: 4528d9a64d5769f60ec019340fee3434 SHA1: ac09aa6761b37dc700cb87b4e8516d9995936a24 SHA256: 291821cc3920d5099eeac97e578ae41721de288723796954aeebfcd417ca2e9d 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: 12 Filename: all/perl-parent_0.241-1.4_all.deb Size: 8732 MD5sum: eb120887b8813dbbf60da6d6a381a515 SHA1: c4eeebdfbb527198c0e6e13b014edf319aca968a SHA256: 98db58b04b3193898c946abd2816c685920c2912a18d8885831bb955c84c6b04 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-3.4_all.deb Size: 15484 MD5sum: 732b1aa81380735445dd6741df9589ed SHA1: 76d67742f51e425ac132db7f5463a1c3a9638d73 SHA256: bb2ed76bc0a75e3114a730469fe9665fceba6fc8224d815b819e5b734e364a1c Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Perl-OSType/ Description: Map Perl operating system names to generic types Modules that provide OS-specific behaviors often need to know if the current operating system matches a more generic type of operating systems. For example, 'linux' is a type of 'Unix' operating system and so is 'freebsd'. . This module provides a mapping between an operating system name as given by '$^O' and a more generic type. The initial version is based on the OS type mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft operating systems are given the type 'Windows' rather than 'Win32'.) Package: perl-pod-coverage Version: 0.23-3.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-3.7_all.deb Size: 18472 MD5sum: dc8ef0f6586676e03de28b4dcc9b0841 SHA1: 7a416cce015a81f60488068464cba872d91ffd01 SHA256: 1e71c2b7c2af3d171e062292b52feb0e4292c2d7baf145fe1f2b2b49acad17c1 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Pod-Coverage Description: Checks if the documentation of a module is comprehensive Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, _perlmodstyle_ tells you to, so you must obey. . This module provides a mechanism for determining if the pod for a given module is comprehensive. . It expects to find either a '=head(n>1)' or an '=item' block documenting a subroutine. . Consider: # an imaginary Foo.pm package Foo; . =item foo . The foo sub . = cut . sub foo {} sub bar {} . 1; __END__ . In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo' package is only 50% (0.5) covered Package: perl-sub-uplevel Version: 0.2800-2.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-2.12_all.deb Size: 22440 MD5sum: ff04be220fb35dc748538d350b636507 SHA1: b690582e189302978f538215ef34324a4e4b22ce SHA256: c95320f147806c17e20910b51b97e3acd088eed6c76c08c15745899169e72b31 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Sub-Uplevel Description: Apparently run a function in a higher stack frame Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided. Package: perl-test-class Version: 0.52-3.20 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-3.20_all.deb Size: 56398 MD5sum: d579e5d0ff7fc6d2cd04ee4153251d68 SHA1: 955c2a21afc1b206fcb566830068540a1812b88f SHA256: ca81e7d8b4e5c46f756d7bad07b5cb8266282dbb0971ab1cc6c5bd8421e6c208 Priority: optional Homepage: https://metacpan.org/release/Test-Class Description: Easily create test classes in an xUnit/JUnit style Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. . Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). . _Note:_ This module will make more sense, if you are already familiar with the "standard" mechanisms for testing perl code. Those unfamiliar with Test::Harness, Test::Simple, Test::More and friends should go take a look at them now. Test::Tutorial is a good starting point. Package: perl-test-compile Version: 3.3.1-3.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-3.10),libtest-compile-internal-perl (= 3.3.1-3.10) Filename: all/perl-test-compile_3.3.1-3.10_all.deb Size: 20016 MD5sum: 5f56a2a572cf27f0b4e48d3684ff2db2 SHA1: 234d6b3f314fda11655fe8f7aa5098b0223b5522 SHA256: 4ed5defde9cabcb8ba25aebc96e35291746b71a4cb149d93b09b46d6c0c89a36 Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Assert that your Perl files compile OK 'Test::Compile' lets you check the whether your perl modules and scripts compile properly, results are reported in standard 'Test::Simple' fashion. . The basic usage - as shown above, will locate your perl files and test that they all compile. . Module authors can (and probably should) include the following in a _t/00-compile.t_ file and have 'Test::Compile' automatically find and check all Perl files in a module distribution: . #!perl use strict; use warnings; use Test::Compile qw(); . my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.204-4.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-4.7_all.deb Size: 88526 MD5sum: 656ae24a90be03e57a25f65756b5b1d9 SHA1: ae79f8aecbe586a80c294f090d3b93400a9a4e1d SHA256: 762301245d917725f87fd66eee06e034994ad309d111f8a7a6944beb288e1377 Priority: optional Homepage: https://metacpan.org/release/Test-Deep Description: Extremely flexible deep comparison If you don't know anything about automated testing in Perl then you should probably read about Test::Simple and Test::More before preceding. Test::Deep uses the Test::Builder framework. . Test::Deep gives you very flexible ways to check that the result you got is the result you were expecting. At its simplest it compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop. . Where it becomes more interesting is in allowing you to do something besides simple exact comparisons. With strings, the 'eq' operator checks that 2 strings are exactly equal but sometimes that's not what you want. When you don't know exactly what the string should be but you do know some things about how it should look, 'eq' is no good and you must use pattern matching instead. Test::Deep provides pattern matching for complex data structures . Test::Deep has *_a lot_* of exports. See EXPORTS below. Package: perl-test-differences Version: 0.710.0-3.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-3.7) Filename: all/perl-test-differences_0.710.0-3.7_all.deb Size: 18548 MD5sum: f45c0e95d9222a2e7409d85c5512292c SHA1: c67c3d40d24449bbc88c1468fdad2ec0351e04fd SHA256: 2c665fa28c6db115a1c0630270b1d2fd515ffa3327ee512427adb116091c4ad4 Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-exception Version: 0.430000-3.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-3.13) Filename: all/perl-test-exception_0.430000-3.13_all.deb Size: 18206 MD5sum: 6e298efe2a64aa6021420c827499d6db SHA1: 8726c5205d44dae91c644940c394cdd3f0d70412 SHA256: 3bec3c8d2658c0b1d52bc1f6c2c2879dec52872b7923b50b11c7d73eb1bacdfb Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Exception/ Description: Test exception-based code This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends. . If you are not already familiar with Test::More now would be the time to go take a look. . You can specify the test plan when you 'use Test::Exception' in the same way as 'use Test::More'. See Test::More for details. . NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping program execution - including exit(). If you have an exit() in evalled code Test::Exception will not catch this with any of its testing functions. . NOTE: This module uses Sub::Uplevel and relies on overriding 'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If this use of global overrides concerns you, the Test::Fatal module offers a more minimalist alternative. . * *throws_ok* . Tests to see that a specific exception is thrown. throws_ok() has two forms: . throws_ok BLOCK REGEX, TEST_DESCRIPTION throws_ok BLOCK CLASS, TEST_DESCRIPTION . In the first form the test passes if the stringified exception matches the give regular expression. For example: . throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file'; . If your perl does not support 'qr//' you can also pass a regex-like string, for example: . throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file'; . The second form of throws_ok() test passes if the exception is of the same class as the one supplied, or a subclass of that class. For example: . throws_ok { $foo->bar } "Error::Simple", 'simple error'; . Will only pass if the 'bar' method throws an Error::Simple exception, or a subclass of an Error::Simple exception. . You can get the same effect by passing an instance of the exception you want to look for. The following is equivalent to the previous example: . my $SIMPLE = Error::Simple->new; throws_ok { $foo->bar } $SIMPLE, 'simple error'; . Should a throws_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 3 - simple error # Failed test (test.t at line 48) # expecting: Error::Simple exception # found: normal exit . Like all other Test::Exception functions you can avoid prototypes by passing a subroutine explicitly: . throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . A description of the exception being checked is used if no optional test description is passed. . NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will automatically add the current script line number, input line number and a newline. This will form part of the string that throws_ok regular expressions match against. . * *dies_ok* . Checks that a piece of code dies, rather than returning normally. For example: . sub div { my ( $a, $b ) = @_; return $a / $b; }; . dies_ok { div( 1, 0 ) } 'divide by zero detected'; . # or if you don't like prototypes dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' ); . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . Remember: This test will pass if the code dies for any reason. If you care about the reason it might be more sensible to write a more specific test using throws_ok(). . The test description is optional, but recommended. . * *lives_ok* . Checks that a piece of code doesn't die. This allows your test script to continue, rather than aborting if you get an unexpected exception. For example: . sub read_file { my $file = shift; local $/; open my $fh, '<', $file or die "open failed ($!)\n"; $file = ; return $file; }; . my $file; lives_ok { $file = read_file('test.txt') } 'file read'; . # or if you don't like prototypes lives_ok( sub { $file = read_file('test.txt') }, 'file read' ); . Should a lives_ok() test fail it produces appropriate diagnostic messages. For example: . not ok 1 - file read # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. . * *lives_and* . Run a test that may throw an exception. For example, instead of doing: . my $file; lives_ok { $file = read_file('answer.txt') } 'read_file worked'; is $file, "42", 'answer was 42'; . You can use lives_and() like this: . lives_and { is read_file('answer.txt'), "42" } 'answer is 42'; # or if you don't like prototypes lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42'); . Which is the same as doing . is read_file('answer.txt'), "42\n", 'answer is 42'; . unless 'read_file('answer.txt')' dies, in which case you get the same kind of error as lives_ok() . not ok 1 - answer is 42 # Failed test (test.t at line 15) # died: open failed (No such file or directory) . A true value is returned if the test succeeds, false otherwise. On exit $@ is guaranteed to be the cause of death (if any). . The test description is optional, but recommended. Package: perl-test-most Version: 0.38-3.19 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-3.19_all.deb Size: 23410 MD5sum: f74179232d9b0e544f1374db37ba18fe SHA1: 4509de935cb12c9719d69521025bb822e58d2b03 SHA256: e3f118d373152bbf97b07156311f41ec019a3a990d62f9cc82c296e95f3eb811 Priority: optional Homepage: https://metacpan.org/release/Test-Most Description: Most commonly needed test functions and features Test::Most exists to reduce boilerplate and to make your testing life easier. We provide "one stop shopping" for most commonly used testing modules. In fact, we often require the latest versions so that you get bug fixes through Test::Most and don't have to keep upgrading these modules separately. . This module provides you with the most commonly used testing functions, along with automatically turning on strict and warning and gives you a bit more fine-grained control over your test suite. . use Test::Most tests => 4, 'die'; . ok 1, 'Normal calls to ok() should succeed'; is 2, 2, '... as should all passing tests'; eq_or_diff [3], [4], '... but failing tests should die'; ok 4, '... will never get to here'; . As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the import list, the test program will halt at that point. . If you do not want strict and warnings enabled, you must explicitly disable them. Thus, you must be explicit about what you want and no longer need to worry about accidentally forgetting them. . use Test::Most tests => 4; no strict; no warnings; Package: perl-test-pod Version: 1.52-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-3.4_all.deb Size: 13378 MD5sum: e9809d1b05f4e5afee516ae8dc787527 SHA1: 757edd246164de0acdeb41f617c780f89ef7910a SHA256: 276ff457c87198c75e584e46c4b0d1405508ed708f1b33ab3136d6e3dc9fc051 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod/ Description: Check for Pod Errors in Files Check POD files for errors or warnings in a test file, using 'Pod::Simple' to do the heavy lifting. Package: perl-test-pod-coverage Version: 1.10-3.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-3.7_all.deb Size: 10806 MD5sum: 7a59a398dab44e87fbf3ce9c972e1dd4 SHA1: 5cf8bd53f489f23b364b45b5cd651e37b4cd4590 SHA256: 96040cd48a0937c558bc453b6d1ccd3ae250e69cce0624f204639c7f474eb66e Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-test-warn Version: 0.37-3.13 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-3.13_all.deb Size: 14820 MD5sum: 18963feee1995a4c78ca42df07f169d4 SHA1: e3f7fc68d6469e54d7ed28b633044fb9253d15cd SHA256: 4668f61c2ab77e5acf399e4eddc58e50714cbacbb75e77a81e8bb9400e221b5e Priority: optional Homepage: https://metacpan.org/release/Test-Warn Description: Perl extension to test methods for warnings A good style of Perl programming calls for a lot of diverse regression tests. . This module provides a few convenience methods for testing warning based-code. . If you are not already familiar with the Test::More manpage now would be the time to go take a look. Package: perl-text-diff Version: 1.45-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-3.4_all.deb Size: 32926 MD5sum: d2e19686d0321711a70602aa24923d92 SHA1: 628f99942c02c85dc655b82cfdd20735dc6a90eb SHA256: e6738e4b6bff4b356565adebeffec3c11c89dd5805eee9c9501d0fae92f88371 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-3.4_all.deb Size: 24330 MD5sum: 9d414e1321d534c044c2e9f1404689a7 SHA1: 3fd1763e98e431d973696b3d0d3a999cab5b136d SHA256: a96e0f405d7da46c3524bedf848c712ea43db492071e99e3792ec6e9f66efc97 Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-3.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-3.4_all.deb Size: 8696 MD5sum: 39a4a5c46ed6da5757d714176c05b99c SHA1: 7ee1759b2353c8723b2efb2aaf2a24048fc59486 SHA256: 96a7b445d02b4e5319cb86e0af39524ae435124ea18fa6de4e30ee4ae451e1fa 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.