Package: deb-perl-macros Version: 0.1-2.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-2.2_all.deb Size: 2574 MD5sum: 4c2bd38e5a1926d40a70348ec44ae00e SHA1: 3790bcbae6c0db6ebff38b2855a18083306a5722 SHA256: db474cb57f3d73ab057434fd074635adcbfa5da2ef0d08b61a5e842c97493d73 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.09.0-2.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.09.0-2.1_all.deb Size: 55362 MD5sum: 7811ce7743070ff345053d02ad76b903 SHA1: c9b48c6c35e266bf425e69d9e87c961954059443 SHA256: 6563c5b8ad3826f448845f998be2a43747231b27e9fdd82878de5bdf05c31fab 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.09.0-2.1 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.09.0-2.1),liblua-api-perl Filename: all/debbuild-lua-support_24.09.0-2.1_all.deb Size: 8246 MD5sum: 14d0bb47c02d12b94606b216af39fca0 SHA1: 52149a2fc810b9344da96dd85e7dde1d057d0f7f SHA256: e3be7f585819cff3d224cdc8adeabdf3d7df3f46886614f7ef016a427ffa408d 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 854 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-45.2) Provides: lua51-libs (= 5.1.5-45.2),liblua5-1 (= 5.1.5-45.2) Filename: amd64/liblua5-1-5_5.1.5-45.2_amd64.deb Size: 346830 MD5sum: cf8523e262ce4826ddea3d5ded3f23e6 SHA1: 82cf6a6fb234a56e7ee8653b7e102f5fc08c4fa2 SHA256: afad294b0c0b65b4dbf1db762c0750c9815523075ff826587a15eb7b98576cd3 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1476 Depends: dpkg Provides: lua (= 5.1.5-45.2),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-45.2_amd64.deb Size: 427832 MD5sum: 78a4bd1c367cd66b96492c64e6cbc372 SHA1: 1d091177c7696cf6d42d421047c09b40b86253f5 SHA256: bcd9e67a21902685fb1f757b64ea471a17b1e247a4b026795a27ec3e32f1102f 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.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1693 Depends: liblua5-1-5 (= 5.1.5-45.2),lua51 (= 5.1.5-45.2),lua-macros,dpkg Provides: lua-devel (= 5.1.5-45.2),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-45.2) Filename: amd64/lua51-devel_5.1.5-45.2_amd64.deb Size: 443012 MD5sum: fe474879d1178f6357a5d91a9aad29ad SHA1: 1268fafb2d63b7557aef0540b01494ffce049c4e SHA256: e71f5ed46de38458b4fd5d4501e1dc2b7ed61b97cac4caab0dff0abf0042f011 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-45.2_all.deb Size: 73398 MD5sum: f1e4fb40e3b7138698480593328cfc2b SHA1: 4884dec45213c71bd83325a5f50121d50e431da0 SHA256: 34f234250e2a818026294c987813844771c55dc76cea068bed11facf4e3df033 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-3.2_all.deb Size: 30202 MD5sum: c3cde86ade0ac3edcc21f2f2cb0c378a SHA1: 0ef083ccfa164e6517fc37ad3189a23e60dd3a4c SHA256: be94834fe53bf0c6652b7bb3e62c385077e209a09ac9c56f1513421fe06e7a14 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-3.2_all.deb Size: 22974 MD5sum: 1c775e5793b6a0ea5bda35407b363eb7 SHA1: a584c1f27f08168b74dac54eceb3cf3c83b82d12 SHA256: 06e2e47eb7dbc1231e7f3f8f6851bb61d1ff759ca1c15073d4eed4f56ba4a344 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-3.2_all.deb Size: 6996 MD5sum: 757e2e9fcfcf3fd1d51894bc00ead11c SHA1: d41c8903e0fa2d51222a50e791ebf71dfea6224b SHA256: 781fa355338ae8f78247446f9616a9a0c4e9b8cb3d878deb1c1586db76843f95 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-3.2_all.deb Size: 28314 MD5sum: 6f9696bde3e57fd8100857ed06bfac5a SHA1: 0e519ebfe193e73cc6e9150704d88e6df56851d9 SHA256: fef1c2f0cbbea09d5ad2be82c83de8f31fbcc99f5bd8d6fc19ebccedf18e5174 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-3.2_all.deb Size: 14508 MD5sum: f7ed22235e65cd94481b12094c5e8819 SHA1: 43b2ee207a88cf57c1164ca6980ce3eed462f9c6 SHA256: 98282f569eccd4878254650be39d2053f98479383a0fcfd281ff90518334724b 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-3.3_all.deb Size: 38922 MD5sum: 029fa78684caeda62656658fd331508d SHA1: be933cec5f16ae1f58d07665c3c86378faf48022 SHA256: 2f49a8310346f65426fca73413688252ae9565a78c407b12a9d9f1c4cf727b6f 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-2.3_all.deb Size: 39258 MD5sum: 89f517fe9d89f8407624ab1301d2ec21 SHA1: 7a6c7bd0e0a484f0e71a60ce55231a0bd7d949e7 SHA256: 26642554c0366d9e718a93860120ed15eee7095c65c8377735a82216bbf50503 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 797 Filename: all/perl-extutils-makemaker_7.66-4.2_all.deb Size: 298292 MD5sum: 0569e4033ea4c45f207338f0acfed74c SHA1: 4664d30e368b8645347e812fee0c05548d12df5a SHA256: 7ec2defc9e3fcc45fca82c1efe36a9a38c118b173bbad53cb333f8f03005b07f 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-3.2) Filename: all/perl-extutils-pkgconfig_1.160000-3.2_all.deb Size: 10476 MD5sum: 5039403ca418bc38fe1913525de62d47 SHA1: 651e1ad8626a8dd84bb6e8694fe16d95856fafff SHA256: 8eccde18cf73ab30b4df955de3cc9daa7729d0d3047544b057431bab2770a2ac 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-3.2) Filename: all/perl-file-path_2.180000-3.2_all.deb Size: 30608 MD5sum: cc52cf0267c11025e4384f0d63889db4 SHA1: 43fc7fa32e84e8bf8ed45eea8cb928783f4a704c SHA256: f3188a044192f9cc1166a1aa31f0abb5ff76110538b666337adb7450aaae3bc4 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-3.2_all.deb Size: 53820 MD5sum: aad5ee845f15f612d1095d03271bd254 SHA1: d42d338a3dff040476babcf1c2e8419ae90ea58b SHA256: 6c05033bccd6295bec433dfa8f819c650f8e96ebfe31ff433d38de7fade3ebe2 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-3.2_all.deb Size: 33224 MD5sum: 186b6f002a9543ba287da3c7922a2e9b SHA1: effb9cd7e256fd50477412f052eba42cadb3c2af SHA256: cfdb5926cbc64b54d0119291a3edd1381416db59dde70fc232a10704808ecab4 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.7 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 709 Depends: perl-base Filename: amd64/perl-lua-api_0.04-2.7_amd64.deb Size: 214972 MD5sum: 0ba4782d99958169d4298d1faf6f545e SHA1: bec091689778383af19500319e971471bda2dec1 SHA256: a6958791afae8da42a3d742a3b9a951fe1f45807fd955d06363bb65b977381e6 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.3 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.3) Filename: all/perl-module-build_0.423400-4.3_all.deb Size: 234622 MD5sum: f5aa7a796009a899bc36fbe8ed822f17 SHA1: 90f19c5ad64bbd6aad91e4f70821c2939e26dc5b SHA256: fa1fb0511fdce30c7053fb4a6ba945cb6f6d8af2f91c18e060add3685afb871f 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-3.2_all.deb Size: 30070 MD5sum: 741d9da0d94460450b33a2af91da2a40 SHA1: b29ac31fb0cf53c5ec3214131370c3c2e0076796 SHA256: 04aa15f0923306f700b710f5432d0d82a182f199cfc939e3734a67107c4ad4b9 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Filename: all/perl-module-runtime_0.016-3.5_all.deb Size: 17728 MD5sum: b6d23e12c5951a396718fd2d65db393f SHA1: d5773567b6d7a1e93710b377f31acabe7e664fa8 SHA256: ad2a525e89085af23229071199c9d2618cdb3d5457a46264f2e8c51a82a07f88 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-3.2_all.deb Size: 17518 MD5sum: 246818a8bf5498fe5a4a186e2c8db26f SHA1: 131ac78303fb48f876d27ced6be65d54d7a2649a SHA256: c96999a8657ef409eacdd8603480f0e8ca55dc74c70cae24e3982eeda2553c14 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-1.2_all.deb Size: 8736 MD5sum: 9e095dea01981205187642340f9ced19 SHA1: 73e73f2a52c4d592cdfb3a9980fef43b4fa2bb1e SHA256: 10e6f0456b65746fc644123a2199a3233e0e00bf42f82424f28b3d24c6c95f97 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-3.2_all.deb Size: 15476 MD5sum: 3800e911fb7bf9b11275f9c61e35fbbd SHA1: b643af0767753f2c148025509061cf2bfe356361 SHA256: 1dcb6c99a2f909c2f151061a60389f486d0c84750ed0587669bb719f02a531c5 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-3.3_all.deb Size: 18474 MD5sum: e400437e26b697d32b26acf2ce172f82 SHA1: a5afa5eac69a05e5163e74fad87a3aeef83745ff SHA256: 1823e6374840ae9f6c02374996f2b4e24137d57e6d6c346083c935dc6d179524 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: all/perl-sub-uplevel_0.2800-2.4_all.deb Size: 22426 MD5sum: bfde8fffdff92df4cd3f3e48864baa17 SHA1: c8c6faffc99f116d97db054b3f08b92555a19e48 SHA256: 0d5a6a6558309d4350f97c766623471ca5a9c13a58b7de90ef31e6da06104c90 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 163 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-3.7_all.deb Size: 56414 MD5sum: 54a31659da611a771278ee70bebc3acf SHA1: 4603cf6ec14564039488b68f7130666f6612f53f SHA256: 0c20812309b7cfb8e6189eea58f85f09f508801a1a5125b89f1ba28dd93568fe 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-3.4),libtest-compile-internal-perl (= 3.3.1-3.4) Filename: all/perl-test-compile_3.3.1-3.4_all.deb Size: 20016 MD5sum: 344fd5d9a947d35f3c8b1e3187be7558 SHA1: 6c6d7f220136bfad56f062ebd81fe9ab08c3d69c SHA256: 372aae958c84822a1f06519bc4086cd6f706c717ddc9aa376eda4a2c20e17223 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 266 Depends: perl Filename: all/perl-test-deep_1.204-4.3_all.deb Size: 88530 MD5sum: 2e5e2ced5c5fec03a4622d319f64bfcd SHA1: ae02c620f214cb73481df2f7e769da4caab9cb22 SHA256: 353071a2f3b261e15597b5fb1fe254c55aca7752d71a4f569d0753f83399e213 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-3.3) Filename: all/perl-test-differences_0.710.0-3.3_all.deb Size: 18554 MD5sum: ea6f4403b319ec89bdc18a3f4ac92731 SHA1: e9b6453b0c589f19043297792bab4764d7e397ca SHA256: eabf9b78028d7a31bd2ec13f1166a197938ce24b983ec649edfb0de4ec756162 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 31 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-3.5) Filename: all/perl-test-exception_0.430000-3.5_all.deb Size: 18204 MD5sum: f79bde6a55340e085e3b99536f844b29 SHA1: 15f2dc2685f21cdbb9b756c42db1a88d06da51f8 SHA256: 0aebb9bf8d70eeed3269bf54e0b81c3f80ffe80c8b8a6172c5ce7ef6dd58b661 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 42 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-3.7_all.deb Size: 23404 MD5sum: 976ab002f97fbd71d3cd4fec295a169c SHA1: e3daf7675d8a043d3554750d349f5da233bebbb9 SHA256: 73bd0b611749f38af169b366c7e37ecf265b8ab0d216f0d4dfb1ca349c5e395f 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-3.2_all.deb Size: 13372 MD5sum: af9e703dc369e75a7232ad6035ad9067 SHA1: a98293504f813ec1b26c642f6deb2682537e37c3 SHA256: 34fe5377896c849130df52983159c0a02e68e859ac280b452f25a7480c9bba33 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-3.3_all.deb Size: 10796 MD5sum: f0818fc8ad246515ca9d90eeb825a7e3 SHA1: d0f180f1e8a893f2132bcbe64856f4529f8bed1c SHA256: ed23cf5b40bc91c5ffbd2f2242949777f412b75c0b9425aa7e1fbe8b9e88bf2a 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 29 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-3.5_all.deb Size: 14820 MD5sum: b6c73d20c54483829c7a168a67822657 SHA1: 50daff178448e9db09e6ee8ce883caf4a628ff54 SHA256: 5fdb40cfe50bc8843ebeb107e5a7ab3151c13f8d7c0176f038be45d3b01d18b2 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-3.2_all.deb Size: 32920 MD5sum: f3de183d7f7b2d96798581e268bfe512 SHA1: e8812e44fca42dcc3773dcc2c7c06974e80e4bdb SHA256: c92c9ee5658622b268d10cdc46f185d6b332f6582ac15fa1c87e42a870cf03a3 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-3.2_all.deb Size: 24332 MD5sum: 9cf7d4e75498ec9555b81fafd54fef0a SHA1: 30875891b75f2f2e8e3244fd951b7798ab1aa4dd SHA256: ba7005cd3814220899559dffe128f60c92eb4c39357dc4609d304fc20965b921 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-3.2_all.deb Size: 8698 MD5sum: 9828dac46f5e2bf97d9a73a5011e9049 SHA1: 8f1f9f23e1ca223e3d26f877fbfede593b9f511b SHA256: 69d2323afde3eb0b5f6d5643482316408f8b05a168ca075312e12cf840846436 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.