Package: deb-perl-macros Version: 0.1-1.1 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: ./all/deb-perl-macros_0.1-1.1_all.deb Size: 2556 MD5sum: 1120754b3a9160ddda912fe9a687cedd SHA1: c5edce68a304aa17dcff16aa641fb01635d8cab6 SHA256: 75a0f1b8f5640313bdffdf660d42f1a18fd4f858f50686ba75b6a4c4d4413bb0 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: 21.01.0-3.1 Architecture: all Maintainer: debbuild developers Installed-Size: 199 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 Suggests: rpm Filename: ./all/debbuild_21.01.0-3.1_all.deb Size: 47600 MD5sum: 1fc20256ce6e85692cc6b8ac6b763971 SHA1: 6e5e847c91124da97d8ed55c6ba0f43f8920a056 SHA256: 4876d7ae3add08c248bdbd7c5b45230efcd5a0e776eeb6aeed51af384fbd82df 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: liblua5-1-5 Version: 5.1.5-47.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 856 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-47.1) Provides: lua51-libs (= 5.1.5-47.1),liblua5-1 (= 5.1.5-47.1) Filename: ./amd64/liblua5-1-5_5.1.5-47.1_amd64.deb Size: 243492 MD5sum: 254bc463689b5a6a2a53eeb4c4ffe0df SHA1: 1ffc70d9d04a596a60769af2869f4aa995115abb SHA256: 6498fa0eea54e5bd44c325e11c71ebb558fbd6e0febac2dd8a503773c4115589 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: 20170611-12.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 37 Depends: lua Filename: ./all/lua-macros_20170611-12.1_all.deb Size: 1532 MD5sum: aaecaf06330bfa7e18eb611aaa7fdef4 SHA1: 068a043ec982b431f63997f8880a79dc29d0547b SHA256: a1d631b0d78d9115767d78f3d1af75576972ea4dedbeffcc0d393d7a414d0b4a 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-47.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1486 Depends: dpkg,libreadline7,libc6,libtinfo5 Provides: lua (= 5.1.5-47.1),lua-api (= 5.1) Filename: ./amd64/lua51_5.1.5-47.1_amd64.deb Size: 300652 MD5sum: 84650485b81676ec7c980ddfc13eb602 SHA1: e63537fa482e0199cae8e16d3d757fa8e08a9574 SHA256: 02b7f3e0df1573a0f0091eb3f0bf84b165d9532f12feb2fb5bdcce524fc943ad 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-47.1 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1529 Depends: liblua5-1-5 (= 5.1.5-47.1),lua51 (= 5.1.5-47.1),lua-macros,dpkg Provides: lua-devel (= 5.1.5-47.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-47.1) Filename: ./amd64/lua51-devel_5.1.5-47.1_amd64.deb Size: 313940 MD5sum: 02b7d229e9e1983422341ee3c1531c82 SHA1: 72a5f9c9572709e39519ce859ff7a8d7fa70240c SHA256: b8c809efbeeef9506c786d6081a81f4e789d32e464380f077d0b3aacd094eec1 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-47.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: ./all/lua51-doc_5.1.5-47.1_all.deb Size: 71672 MD5sum: 3f5aa571e0fa9777dfd3173ae796201d SHA1: 39caf3fa40b4f67d86c5b62da738bdf89e1dfe21 SHA256: 265c7d541cec7c81f65dc57c8b518281e683641cfc32af0f1c53271e3a257d44 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-48.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: ./all/perl-capture-tiny_0.48-48.2_all.deb Size: 29928 MD5sum: c78d982333d7a0771d5448465f1220e3 SHA1: 4be9120d7bea741decb55e386a9bbb786def0171 SHA256: e2b1a61293dca5248eababf7e21258d8f2eb2573cccc7199cd085e15d266703a 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-2.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: ./all/perl-carp_1.50-2.2_all.deb Size: 22604 MD5sum: f02f5a5a9f2d3b8589728583b5dec87f SHA1: 482e8cdc33bb881074cc517d963d55ce76a8c68a SHA256: 099f3d680d83dade8a4b3479f47c755a6f135067b0f3267a5a84c036a48ef1de 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.08-140.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: ./all/perl-class-data-inheritable_0.08-140.2_all.deb Size: 7508 MD5sum: bfd8d4e18ba7f2d1c290372b15197181 SHA1: 900b1aa9b8a1f2f455b63d85428789a63a6f0069 SHA256: 40670ba8a5952f3580a9a38d151d2f577e703553fff7c6b5b9921311d83e0def Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/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 overriden. . 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); . $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: . 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 overriden a method: . Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu futher changes by Pere::Ubu no longer effect Raygun. . Pere::Ubu->Suitcase('Samsonite'); . Authors: -------- Original code by Damian Conway. Maintained by Michael G Schwern until September 2005. Now maintained by Tony Bowden. Package: perl-devel-stacktrace Version: 2.04-43.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: ./all/perl-devel-stacktrace_2.04-43.2_all.deb Size: 28304 MD5sum: 61cb71bb6aa986ec0f2a7f3d65604dfa SHA1: 4afa6d04fb737fda14de159ed2af08aaac000346 SHA256: 1e0c6265a427bfdc25ab7aa66802ead5661091d164abad3f3914301b8d959448 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-63.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: ./all/perl-devel-symdump_2.18-63.2_all.deb Size: 14284 MD5sum: b92658e4a29b666f09ee8cb2e1221123 SHA1: a39ba185a27b3ef897b995e072e320390d7c6298 SHA256: b5d802af564ea43686eaf5f941f59cb907c305166ae1ef212618ed349f6d83ca 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.44-41.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 136 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: ./all/perl-exception-class_1.44-41.2_all.deb Size: 36820 MD5sum: 3a9792b737a9d2634fe6334b70b017ab SHA1: 467f16baf3a3e6e67ff506e7711286650669c5ba SHA256: 4564399a89bf0caa55b7cd113d12e707163c35377bb7309cb98024cd2e61aac4 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/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-36.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: ./all/perl-extutils-cbuilder_0.280236-36.2_all.deb Size: 39136 MD5sum: c0f239a333dd0ddf002ffed07844b1f6 SHA1: 8d83abe068e739437fabbfd5301f2a2b83964c07 SHA256: fb6e4912a52f39d61a6b9f796b0ad1ecfb33ba61a33d67ca4305e115265492fd 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-pkgconfig Version: 1.160000-52.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-52.2) Filename: ./all/perl-extutils-pkgconfig_1.160000-52.2_all.deb Size: 10480 MD5sum: 3b0e36e2250d376f5cdfbba6c09d9225 SHA1: b6c9e5193981892b587bdca5eda4d8ac479e124d SHA256: 45c437b54ab2f81e43240aea67c2480ce98df6340054ee0d8ae83e002bc6d91b 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-21.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-21.2) Filename: ./all/perl-file-path_2.180000-21.2_all.deb Size: 30580 MD5sum: 180f39bebe36004269f997039ee32e77 SHA1: 8cc02e239f5c46ef46a72e740c4fb83a8514dada SHA256: 1d78aee7619e47cfabc6f7735ef071049883660cfcd647b1daad58937134e246 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-21.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: ./all/perl-file-temp_0.2311-21.2_all.deb Size: 53248 MD5sum: f9ca9916a05022b4017906adab087055 SHA1: 4b649b852e6abc6473e14d901c0dc2c884ad6bb6 SHA256: 6eed8f2b914ac3c462812ebb60f162371b97e9bbeb0760ac83dbaa5c5c880b18 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-2.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: ./all/perl-ipc-cmd_1.04-2.2_all.deb Size: 33076 MD5sum: 5bb8c3f361ed114fb05055f47af37742 SHA1: 2004245af8c3dc6f63e1ad1ae9c61de57ce10732 SHA256: f747bf8c203bf281cbdeaf5431f62528664f21d0a034087011cf4c1887ba1462 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-11.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 793 Depends: perl-base,liblua5-1-5,libc6 Filename: ./amd64/perl-lua-api_0.04-11.2_amd64.deb Size: 174680 MD5sum: 9c6e3eabe032d2597c77802aab898b5e SHA1: 0ad7938e4cc42220c875490f378e67117e4abd6e SHA256: f4a466733fe76686acf25448819881747802052f0bb86e2382d7f2929f9ee6d4 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.423100-51.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 711 Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype,perl-version Recommends: libextutils-manifest-perl (>= 1.54) Provides: libmodule-build-perl (= 0.423100-51.2) Filename: ./all/perl-module-build_0.423100-51.2_all.deb Size: 244148 MD5sum: 924697d752335a94864ad0e8a2cde117 SHA1: ef4949445db7ba67687b5666950e2487a827905c SHA256: d83c6c8c96d0a30e6900016aec03122f0d48f77e5557f805249bce27571115a2 Section: Development/Libraries/Perl 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.000037-17.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 110 Depends: perl-version Filename: ./all/perl-module-metadata_1.000037-17.2_all.deb Size: 29600 MD5sum: 48a3ef3e0fa28fdd765362cca4e2ec07 SHA1: 7538889f3198f12a648fb7a194a42055d519f97f SHA256: 2c891589f185b3d2835c0c4d2ae6789b21378efd600cce06cd8d71b2ac9ccf9f Section: Development/Libraries/Perl 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-23.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Filename: ./all/perl-module-runtime_0.016-23.2_all.deb Size: 18352 MD5sum: 7d549a75ac3a08c8d25cbd3c4f62271e SHA1: 7c602c94c18a0b4508c668c48d92dc67490aa703 SHA256: 45f83b8f0532dd111802f1bbd1d6f97bb30b30297c68f07cf60efb3b1b5f57c8 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.13-33.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Filename: ./all/perl-mro-compat_0.13-33.2_all.deb Size: 11060 MD5sum: 7bf0624b67e7e4ec7cabe5496a1142ec SHA1: 5cf4e2c4f3238eaa440118bbebdcc6a36aaf1127 SHA256: 4c390650b182bffba80bce0039c7f8584effc4f2558d36166acb2975f7bb8bbf Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/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.238-2.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 47 Filename: ./all/perl-parent_0.238-2.2_all.deb Size: 8240 MD5sum: 4c1bd3db85935c9cb4610742603891c3 SHA1: 278b52d57cbc45d51a20e686f57139d76e578639 SHA256: c75e1d08f6e0638d4fe7d0c9ba5fd4220f48145d7ec928c95dbc1e32c1e0899e 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'; . 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-2.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: ./all/perl-perl-ostype_1.010-2.2_all.deb Size: 15072 MD5sum: 28387a73ad181342f0e433e93ae43add SHA1: 949cbffcbd545d658d87a062b4f366b2924e045c SHA256: 008f32430348ab271aca70dd277f3d2184087fed1ca59d84b883cb4c4681d2ff 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-32.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: ./all/perl-pod-coverage_0.23-32.2_all.deb Size: 18948 MD5sum: 0f3f4a3b93ac217741ed028c61fd600f SHA1: 10880c1a106c94c77917264ede421cb6749860e5 SHA256: 8610dddbc2ea25797dfe3a22bdddd8ad192667d5400f8aadde7fd34bb0d38fb9 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-35.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: ./all/perl-sub-uplevel_0.2800-35.2_all.deb Size: 22140 MD5sum: 4b22c8ee064adfc4ef7a6bc222f05e89 SHA1: 8b6cd4a8b85adba6d209b9e2e1fb526855274912 SHA256: 0b42bc0436bc629da7d086a46ff4a2c58a7084f012bebce0f8ea4bdcc6e43764 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-29.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: ./all/perl-test-class_0.52-29.2_all.deb Size: 56680 MD5sum: 5b011c54854eccf7f5e2980e469a0b01 SHA1: 10915ba96bafedfda0392895706c01e1ae3f1aa7 SHA256: 3c9d20de8fbe65578605502bac3b9db11073f2480f25961f4d111bc87aba8b35 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: 2.4.1-26.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: perl-base,perl-universal-require,perl-parent,perl-version Recommends: libdevel-checkos-perl Filename: ./all/perl-test-compile_2.4.1-26.2_all.deb Size: 20344 MD5sum: f556c0260f4add1d6179f17536d398da SHA1: d27b40fed921ba725ad92245925fd17c6d76884e SHA256: b8057e947ec91c276c2c07568dde0551c97b81809d8503e0bc20964d03cab1d7 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/Test-Compile Description: Check whether Perl files compile correctly '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: . use strict; use warnings; use Test::Compile; my $test = Test::Compile->new(); $test->all_files_ok(); $test->done_testing(); Package: perl-test-deep Version: 1.130-42.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 165 Filename: ./all/perl-test-deep_1.130-42.2_all.deb Size: 47000 MD5sum: 6aab52716a1ef7191b31ffeaaa77e4de SHA1: 193a9fa8ed6e2f4f1afb870e968c336884476714 SHA256: 3d1139131dc20bd29406887881b7617ac54c9059289f8dfdf729c4804a09abbf Section: Development/Libraries/Perl 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.67-36.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-capture-tiny,perl,perl-text-diff Filename: ./all/perl-test-differences_0.67-36.2_all.deb Size: 16948 MD5sum: 6c097e737e78fdcd8791cbd1bcfca007 SHA1: 85a35a9a699479cf358d76eab0145fda41e4afdd SHA256: 876afeb95e34da899c085be1745e8fc7d41ecca6ca7b7d918c416dc4a15ad2a7 Section: Development/Libraries/Perl 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 not ok 2 - differences in whitespace not ok 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-92.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-92.2) Filename: ./all/perl-test-exception_0.430000-92.2_all.deb Size: 17916 MD5sum: 31deef15f33c0e421c6499d4b8e40f53 SHA1: 51dbb5673307c206dcec11e6224a4d2fd9c96443 SHA256: fa4f99d170ef68e7fc4f936f78f6f85b213096517f9ee914848c437e4abf772a 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 . 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'; . 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'; . 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 . 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'; 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 . 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.37-20.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: ./all/perl-test-most_0.37-20.2_all.deb Size: 23188 MD5sum: 26c9208288cefc4f3a1db230142afff0 SHA1: bb6b0bc5597854c4796fab644e4d10cd24befaa2 SHA256: 22560f84d3e908372ee403da0d48eb01caf4dd628087d7aaa93158928c65c915 Section: Development/Libraries/Perl 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-43.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: ./all/perl-test-pod_1.52-43.2_all.deb Size: 13240 MD5sum: 0c9167af9f7e0ddb125f9a6581a55e3e SHA1: 9c14876e2429ef6659e7d20ece333f00bd761f39 SHA256: e0b53552e0fb896c1fc160e43e18a21c64c5a6b0db0156cb8f600f09dc84a492 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-278.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: ./all/perl-test-pod-coverage_1.10-278.2_all.deb Size: 10784 MD5sum: 1bffd844db2a99397ef84ed6e99a5424 SHA1: 503a15ad35dae1e0755142568e309cffc1eea8a2 SHA256: 9ab85a6cd8199335a91ccd5713f270f39ce9816dec1a179955fa8ccb71314ce2 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 . 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.36-31.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 69 Depends: perl-carp,perl-sub-uplevel Filename: ./all/perl-test-warn_0.36-31.2_all.deb Size: 14604 MD5sum: b12d5949ecdf6f1e6f15dcd861eedd2e SHA1: 43ec9089ddd3ec1a23be9166812b0eb07e25e913 SHA256: 15f811cd338566fb95c76eb0eaccfa63995a10f1ddb77a88f439858fd5bdb0b5 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/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-33.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: ./all/perl-text-diff_1.45-33.2_all.deb Size: 33204 MD5sum: 57dc970410f288f0953b642f0a547854 SHA1: 99a4055208fb9e36b382f661009101aff8e5e64d SHA256: be80f6ccccc68900f721cb067378c83ee39d8a91e113a41c6b9f51f1cbb8e27c 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.30-47.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 79 Filename: ./all/perl-try-tiny_0.30-47.2_all.deb Size: 23296 MD5sum: 9ba945009d22764ba9012b20b5f58a31 SHA1: 2bc91dcf85605f32e957d9a6582c36c745c42d93 SHA256: fc9243ad57c81d4035d6a415b101518480b0107ba47cb83577a79092017143e3 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/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 learnt the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.18-96.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 51 Filename: ./all/perl-universal-require_0.18-96.2_all.deb Size: 7896 MD5sum: ad3186a32a7093859774e182b9d40189 SHA1: cdb9e1f051a44c029d947ce2c38bab3dbd38adb7 SHA256: 19f1ef57b6650c825c11dec8849b84ef3afca4ca7ceae7195332395fca5d7c41 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/UNIVERSAL-require/ Description: require() modules from 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. Package: perl-version Version: 0.9928-27.2 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 298 Depends: libc6 Filename: ./amd64/perl-version_0.9928-27.2_amd64.deb Size: 91008 MD5sum: 5bb8929f3b5fadcc097abe12bff47871 SHA1: ae479035ce8ad1c29882096c3f1d3757678354ad SHA256: a73bb30a872eb448cc38e073be040c38e7c760e00684f7f551526bfd88518b9e Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/version Description: Perl extension for Version Objects Version objects were added to Perl in 5.10. This module implements version objects for older version of Perl and provides the version object API for all versions of Perl. All previous releases before 0.74 are deprecated and should not be used due to incompatible API changes. Version 0.77 introduces the new 'parse' and 'declare' methods to standardize usage. You are strongly urged to set 0.77 as a minimum in your code, e.g. . use version 0.77; # even for Perl v.5.10.0