Package: deb-perl-macros Version: 0.1-1.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: ./all/deb-perl-macros_0.1-1.2_all.deb Size: 2552 MD5sum: af25fd365802795eb13a9429cba7b31e SHA1: 9efbe633623ae269243cac75b7a5aa3ea50f76e9 SHA256: a1a75ca103c2becb95e12b59ac1c41590f16db686e4bb3e8ae63de77795bbb67 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.2 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.2_all.deb Size: 47604 MD5sum: 4fb485975c9d5a58ba4dc2029736495a SHA1: dbe538dd8eb9c6e18275754198f1c8abe3a647eb SHA256: fd4ebd31fc8f20b219482ce1441830d3f7eb33808de175e2c2662b58d95a766a 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: 986 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: 284260 MD5sum: e0b5dff7daf1018c03a5e07b7a337950 SHA1: e599130a99b92ca599699caf3c13b3189902bb02 SHA256: a6fa9367347efc6f81a399e161fa976e8d0d6e049217bc0c78eeab81785fecc4 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 37 Depends: lua Filename: ./all/lua-macros_20170611-12.2_all.deb Size: 1532 MD5sum: 6aa17266b9b1264295961ff25fdbee8e SHA1: 22a2f7aa27e04a73922311d66ccf52edfeb0d6da SHA256: 5deca1bf153f4b9dd449f14ebb4e0c5efc2bc4a5effc098361cb2d83fecf70f6 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: 1708 Depends: dpkg,libc6,libreadline8,libtinfo6 Provides: lua (= 5.1.5-47.1),lua-api (= 5.1) Filename: ./amd64/lua51_5.1.5-47.1_amd64.deb Size: 359732 MD5sum: 82b1847543a6e2f982a74b214c05cda0 SHA1: e67c1e1aa3616340e0e671fb8671992aee261c06 SHA256: 4969b18acbfbabd8ff3e809b3c7449752085c9bb7d28394154e763d691eee175 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: 1884 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: 363684 MD5sum: 829a3ef437c9fd533289d9b751650bfc SHA1: 4c91f4781a40b2190ff93aeee50e61dc6f8b3726 SHA256: 38617a8e52dd9136ef01e15af5790538d11267f7c30a201867504a77fbf8d99c 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: 71688 MD5sum: 9bc309d9018672271753affe309e4d9c SHA1: 0d08fa05d58cac4d88a4528f732adce34f956f6d SHA256: 10453a4f06d5e01d52b00988b3e8beae988a5ee6aff270e8e8237934cd74e631 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: ./all/perl-capture-tiny_0.48-48.3_all.deb Size: 29956 MD5sum: d729392e70e7e9040ff8f024bacc2dd9 SHA1: 6ce2a3e526bd07e3fe2885f1f093380b5cc1a5ee SHA256: 96fe0072a972c300d96142c69362bd9493a8ba76eb12f0caac104599f0f27dd8 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: ./all/perl-carp_1.50-2.3_all.deb Size: 22620 MD5sum: 3d9a2d959975a568fdfb552fad9e7fce SHA1: 5368280b092848be9f4c5fb7d44ad2e2b9697d38 SHA256: ac577bc413e2988ae4c72fe4e2a4efd44cbef7c0acbeebc11198a8abca046713 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 56 Filename: ./all/perl-class-data-inheritable_0.08-140.3_all.deb Size: 7528 MD5sum: 6084b1c34f5a669761f1418412abf7b6 SHA1: b854c826f421fe6d26a37a603f433b12500572cc SHA256: d7dd34cb09e696ed45ea42233ff50a607c19f783ed38db8d4513b198fc5859c2 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: ./all/perl-devel-stacktrace_2.04-43.3_all.deb Size: 28368 MD5sum: be360d8e8e27be388129a8029b28d31a SHA1: 295dadc753f0f626466feae7757b21508c115573 SHA256: 18fb0d192dbe8baf36bae1d06e3966ec303c70abf72d9fd0d77930534dac365e 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: ./all/perl-devel-symdump_2.18-63.3_all.deb Size: 14304 MD5sum: 69820038f6f5372bf1c47fa0692f4761 SHA1: 25fdad780dcfabe803842b506fe8df6c7a43af2e SHA256: 1e4dacd7e9884453c7b3a828701ae153712b496a25d796cbaf4f0da1f21e0c2e 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 136 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: ./all/perl-exception-class_1.44-41.3_all.deb Size: 36848 MD5sum: 6b7a97212319faf4e91d4b5423d35438 SHA1: 5379bacf881fa4ba3ba5e5b72b72aefdb957923b SHA256: da238b089ca8468965ea50767044c9cf43a8dc8754921986a2b37b2fef3d8939 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: ./all/perl-extutils-cbuilder_0.280236-36.4_all.deb Size: 39220 MD5sum: 5203f9c4307be148db1ab8d4817510a3 SHA1: ec84493ec0d4deb75e819b4ab583ca3841eda1bd SHA256: 7c417b11a65930c8288fb7b90137541747fd3c6caf54bbba88a508be3422d499 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-52.3) Filename: ./all/perl-extutils-pkgconfig_1.160000-52.3_all.deb Size: 10500 MD5sum: a6f6461408e16846db1687ed420b0bcd SHA1: 5d1d04c06392a618df1c84486f823aa325036180 SHA256: 74f9cf1bc185817478afa0b7235ee11df5b5ef2cceaf14004844688c788b5ce2 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-21.3) Filename: ./all/perl-file-path_2.180000-21.3_all.deb Size: 30612 MD5sum: dd954a7515c3f8d7619ba5304212a189 SHA1: 6463189c937a1483da1b98becfb2ed281d24b0af SHA256: 1a9e2c471a86ec5494c48adc34686d3200013ad77cc7b7bba0585f5c8550e1e5 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: ./all/perl-file-temp_0.2311-21.3_all.deb Size: 53244 MD5sum: 8e39eaf7c65eb911c45ae235d067bc53 SHA1: 09f1af422d0812c7de4a1b9b8ce5e60639b63149 SHA256: 9bf62dfb4f1e314122e13fc11449ec91cc3f4fdb18da816258e0bcf75cb786cc 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: ./all/perl-ipc-cmd_1.04-2.3_all.deb Size: 33092 MD5sum: 2d6d7cdd75ce80ca9e04ad7aa4c16ce1 SHA1: 08c1e2b7094d847d89f26ad58aeff70ac73de5a6 SHA256: 3f71774a138d499de0753a396527997e613d9cf6dc191a2db01d7e6f59e9818c 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.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 881 Depends: perl-base,liblua5-1-5,libc6 Filename: ./amd64/perl-lua-api_0.04-11.3_amd64.deb Size: 186452 MD5sum: 8b4c9a4f50f15edb6385ce2d6939cf30 SHA1: a472394d77b9862f95c04f51e7fc64ddacea0d72 SHA256: 39bb0d2f2b4dde90820667effecb3196a620a90d6d6b6cddb65913802e9345bc 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 712 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.4) Filename: ./all/perl-module-build_0.423100-51.4_all.deb Size: 244588 MD5sum: ee282a4fc5255504a56d8d1ce082036c SHA1: 08565267e49ff709b141fdc90823ba10e9e5261e SHA256: d237435f07142b5f8d72286ed4c5efcc35470cbc75c369d6fd6ff5d94994eeb4 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 110 Depends: perl-version Filename: ./all/perl-module-metadata_1.000037-17.3_all.deb Size: 29640 MD5sum: f1d403169c79f94a25203eab386c1d38 SHA1: f77969ba38e09e99511556569a91c42d0f977ca6 SHA256: 0669e06cfbeab9e1ea37ef7a61b2eab8ac9f23df29bea06492a9251c7e31baa6 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Filename: ./all/perl-module-runtime_0.016-23.4_all.deb Size: 18384 MD5sum: 30e6b6b1a2b075e79fa9e22c0ceaa93f SHA1: b9c5f54f9960e3d887df1a336217b8a627b1f0c5 SHA256: 021f226ccca5aedf8cd324be9f5d46faa598a1ef1b633b877a4468eb1757c58e 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 63 Filename: ./all/perl-mro-compat_0.13-33.3_all.deb Size: 11084 MD5sum: 287b647bdebcb1bf92b32ef03337d725 SHA1: a413cc3deb0be075c365463004067444dedca33f SHA256: 6418a803cf88518506a0f047434ba2591eddea84fe871a5413284dbb4ae79667 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 47 Filename: ./all/perl-parent_0.238-2.3_all.deb Size: 8276 MD5sum: 88cd18819a05e2415eb9c66831759e25 SHA1: caf6a7ddceb84d3cad7b03ea69c8e294c7782e63 SHA256: c1c0b5b77bdc8aa9d6a81fe661412eebd0ce755c4e6702e853c08459721eb46a 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: ./all/perl-perl-ostype_1.010-2.3_all.deb Size: 15092 MD5sum: a8ed6328491e899761be2f7eb68f84cf SHA1: 61d52f0fc4d10a0fb9f23015c577d20ba35caf10 SHA256: 681797d75111a668c337d1104d6ce2259b42b6269967949779f75204ca424276 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: ./all/perl-pod-coverage_0.23-32.3_all.deb Size: 19036 MD5sum: d08c3672782942c789e961039ad48c2e SHA1: 9cd1b9af30520d3905f9d3cc87559d8a59277e2f SHA256: 5028adbe10c8caa4a0451d9e603850eaaef81e27523a1cc75e5c02ff169f4b7f 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: ./all/perl-sub-uplevel_0.2800-35.5_all.deb Size: 22176 MD5sum: 283e9a32d2e78ee128380ced18e81c18 SHA1: fe9bab568b1d786881e8f4c8e4ad3f87a57f3c5a SHA256: b7db69d5749bf24a44987937616b06e71462815c863fe15221d9b2c35d352764 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-30.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: ./all/perl-test-class_0.52-30.1_all.deb Size: 56772 MD5sum: 2e2dac5700b0d3d6ab6d98f599d77675 SHA1: ae3c0d22f6ca460f81e4dfb97ddde48370d2bd2e SHA256: 0f77d15b84cc619d10fb2a9f0f22298b0ce7e5d3146bb17f6e25d71d8d265caa 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.4 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.4_all.deb Size: 20408 MD5sum: bdfec9257276aab0192ef5755af1bba7 SHA1: 8e256a95f429ec42a743c9c7783008af0102c195 SHA256: b4c995735c26eef79e72e68ef131ad10c822d5fa793edfb94b980454693a57a1 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 165 Filename: ./all/perl-test-deep_1.130-42.3_all.deb Size: 47076 MD5sum: 75230d9c286a4f34598b43843d80ba47 SHA1: 11d7980e42abca3acbae91c75ff83f9b691bd089 SHA256: 9bf7e794b2a2736ba0e1d194f25bb032c1481326a76b9ea3c9bbe4ca2f8737d6 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-capture-tiny,perl,perl-text-diff Filename: ./all/perl-test-differences_0.67-36.4_all.deb Size: 16956 MD5sum: 520875f48951eab25243048136fcd947 SHA1: 568df8fa9105a24ec84c17c57d058e118a88afd4 SHA256: 05df1ffc6642f419189a0aa125822ccb5ca593e6dffcd40c73205b5c6bc89134 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-92.5) Filename: ./all/perl-test-exception_0.430000-92.5_all.deb Size: 17944 MD5sum: 24bb10144d59580230eac1d5a99ffbe4 SHA1: 0d9c13b15057bdfe5a99de49ad602c3ceb929808 SHA256: 8fa15b6be6e0363971e841e3ef6934f34427f2d8f5a20f1c04e7c376fc2ffa33 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.6 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.6_all.deb Size: 23248 MD5sum: e05eb5e28c906cb47e5c3f49a2c19850 SHA1: 6ebbe1aed3eed1342ac3ffba86d9b17d78913fa9 SHA256: 09979ca95e0b2578298cfc99e9a1dc18b5e951fdd3036f7028b26528d3a950e6 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: ./all/perl-test-pod_1.52-43.3_all.deb Size: 13272 MD5sum: 05b5f1514aedceb673bf9b77e36d2efe SHA1: cc8ff1fc21cd842a4993bea9169fefe2a5e9363d SHA256: 40658582b2689bf311ef673fb474890282597bde97208cd460e1849d9c2581f5 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: ./all/perl-test-pod-coverage_1.10-278.3_all.deb Size: 10812 MD5sum: 2024a8d4f2e2ce3030004fe5c35151aa SHA1: f2964cf42dee4bf885961b4b651be53596601d90 SHA256: e5b799a796300d101c4a99ec40f85954163286fae0e60c5c8b7ce9c57626dc8a 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 69 Depends: perl-carp,perl-sub-uplevel Filename: ./all/perl-test-warn_0.36-31.5_all.deb Size: 14644 MD5sum: 54a9bcf9625bdf00749319601b8233e3 SHA1: 5bae7360e4e2cbc2a7fb024a370b681fe00b5bc1 SHA256: 9eaf2f1e2423f8b22d45f9bab2ed144d450d5bdc5869e593a99694e208f617ec 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: ./all/perl-text-diff_1.45-33.3_all.deb Size: 33300 MD5sum: 005f69742c9e618eb33c04f4b28a5fd5 SHA1: 7ae1328d0c28090a3f0418523bf57fceda2fc99a SHA256: 68602faccfd74f5529110d7706e030f83fa14224e64099a2ff3bda94e6321946 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 79 Filename: ./all/perl-try-tiny_0.30-47.3_all.deb Size: 23320 MD5sum: dbf353c0cc9f213cd0d79b3d9f27eb96 SHA1: 6232d16d55dc17cad3d52d0a1a3ce47f232374b2 SHA256: 7458f9e3c288e9c7424eefbfdfc720c1ea2f26db210020441710eb24f213cb66 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 51 Filename: ./all/perl-universal-require_0.18-96.3_all.deb Size: 7932 MD5sum: 6f6d23fd2bf91f3fae4f142ea9eec9cb SHA1: ea50704fca13a6514efc14daafbc0fd85503515f SHA256: b242b23d69e64647cb8dc39794ef2fd1f1e3706e362b538391b3ccc49f1e5b90 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.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 318 Depends: libc6 Filename: ./amd64/perl-version_0.9928-27.3_amd64.deb Size: 96752 MD5sum: 72cefe48d7eaa99fb014af38b1f90412 SHA1: 3d2947d89239564e8c8d16052ec5cbb511ea9ec9 SHA256: 9f1c522ba92b6c1058f3ce4f3cba8f4be75e5d229515918c7b63d70ed5b84fb6 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