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: 2472 MD5sum: 079f8175043e8c6cf72f58af365170e0 SHA1: a8072e914edd5d5a88cffa0b4fd63b74c4f2cadf SHA256: ade96dff651182c5bfe4f5547f956365593daf689802f6d91656106ae37ca536 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: 47608 MD5sum: 105f11e201b914f6dd10574aae549e92 SHA1: 8ab22c9671d9a494ac2f6eb732cb29aa66f224ff SHA256: 8c996bd4976679cafd5061870c731106c2c04d146bc7b899cf5b0301144a06c4 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: 855 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: 241100 MD5sum: 1021180a25e6f7fe3544035bc12ae7ee SHA1: a8ae5426ca1d0e04087ef304c9d636d83dbfebab SHA256: 91eb0e8948abbc077ee63d1d36fdaa6ae97ac00d4f36ac52bb231a65fde2e7c7 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: 1446 MD5sum: f1bf66c683406cd9dc048713f4b3058f SHA1: e4ff47b92c17ef71c32d8a0733161aef30681d44 SHA256: bec33d35ff2c06fc096420c6a471e603bf6a0684fa59b6564724cfa09edaaae6 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: 1470 Depends: dpkg,libreadline6,libc6,libtinfo5 Provides: lua (= 5.1.5-47.1),lua-api (= 5.1) Filename: ./amd64/lua51_5.1.5-47.1_amd64.deb Size: 292324 MD5sum: 6afbbb8030ab0b0bd45bf8f54d8a97b9 SHA1: 1e6c50ce005df79d2b9a1bd354a4648ba0be6413 SHA256: 8cb194cf296537f2179e7ab1b587a22c9890c53a1f656db213270a30e4b3cfae 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: 1521 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: 310098 MD5sum: 0fe39f814f708b661ccc7e381d6e2e52 SHA1: 52558acbe0c1f92069e52556ec1417c15b0a0de4 SHA256: 68759b97e846fd94570ab1332de24722d9c8448c3800aaa0d7111932a8018d7c 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: 71374 MD5sum: 87cf6bbf5b9abe5cf846c1e3c88f8bd1 SHA1: 0a0f1514561e827fa12491ec5aee0e67810777ba SHA256: 4e06666c7047c2b84f8e2d92e42aa61b8578629dabd081ab8e05c49b9aa0b9ad 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: 29838 MD5sum: 1c759d2108c75d4d0a08634b354f0b2f SHA1: e530bc863292867505ba360d1c4518f647f0dbd7 SHA256: 487f1f62ea20f0f06647a8d83f3e0acaeb632d78eb808197f031069dff041d15 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: 22484 MD5sum: 4e2e96652e96211ad1df97a20553c1a8 SHA1: 4bc0b195633bf053c7c8e9ab4141d548ad827a57 SHA256: 2ce82431f0e295db90538bc6131bcbad3bb6653420d681cd3d2668c0e240f547 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: 7454 MD5sum: 9965745684e7bf8badb6694e0b06da46 SHA1: 6b213021695361fb841e667fe54c25c1f1075759 SHA256: 960dadc6afc0ecf5ae634be23dff047fa15ed1ab36704cfa5d989f3406ce704d 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: 28320 MD5sum: a4ab6b0f124e9b793958e4b0d7f35351 SHA1: 942c9967341b2442c106c22c542581db3fabee92 SHA256: 09e7997a62dbd4d96f982b89de4eec218ed55eafb5812d3865ee87932fbd1baf 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: 14236 MD5sum: 07ec0262f0e55b3115624d9b58e4213f SHA1: 00e0f4893025425d8961ed61c6ec17bd7f677f72 SHA256: 1e91060a16e632ef5b15864bd073f2f2a98516a18da60aa94daa367de27284d7 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: 36752 MD5sum: fd1b55fec7e5534c06d605b934d5e994 SHA1: 082bfa3a05dbeec8ad6d04252f0fcbd96edc9065 SHA256: a26e712223c04b9e0d95c70eaa413a48e4061225806721f2443608c4b2172f38 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: 39066 MD5sum: dfec8a12181e9b4b20ad930b0a446ac0 SHA1: f2dce7fd721956d5c36d7f72e068f810582d7b62 SHA256: 718afe7a084d16eaf82cfd4c514f9ba1233a76b120fc2bf8e3eca26809dc0094 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: 10340 MD5sum: 0d46f1f2a514d6bfd93613f2902d381b SHA1: ebed38204acce3753cc80b82cea3137db53a3dfa SHA256: 796341ddb2e636e6b464c9c9824ef24c0b5aade9925c027bf1b19ad7b3ba20a1 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: 30472 MD5sum: 343af2fb5a21bd647b3ef1f02161615a SHA1: 85f039acf7f289db86439da7b926c384e17b2fac SHA256: 759e959859a8953ba7448536e709c03d29d2a2f793100efcb35e99f097448d21 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: 53096 MD5sum: 4d3087ff7cbdd723f7fa07d327f9d368 SHA1: 850a0c41935896ba1216fc3f647108cff98ff938 SHA256: 6456997617d4483d51fcc5565fac6ed3ce849f515ecb97f4875804dc15ed415e 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: 32942 MD5sum: 09e4d89410e5c837888f772f6e3319ae SHA1: f29766dd827d91cfb2b7218ebf5dbb653efaa106 SHA256: f369b3551fc1ddb543f7e1defbb89be2b8c8416efe88bee49b6fdc8cef0afdf1 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: 759 Depends: perl-base,liblua5-1-5,libc6 Filename: ./amd64/perl-lua-api_0.04-11.3_amd64.deb Size: 165868 MD5sum: dfe33baeb4cf7c2c3e856570861cad75 SHA1: f40efd269214db12d7ba444a7757dc329ed68b37 SHA256: c4545871c96853ebd782fc8247680c11fb27d077740ac8732d67289389bdc153 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: 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.2) Filename: ./all/perl-module-build_0.423100-51.2_all.deb Size: 246500 MD5sum: d59d170df7bc5c6307f2372061cc8834 SHA1: 47c1fe95dcff6341464ca66e7e01e6c329e5530a SHA256: ebcfa9bc5974a1a0bbd90ccabe637d00049ba12549ee4ac3fbde54672de1af22 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: 29460 MD5sum: 410e6395c1c40b4cf3349fd4f608a018 SHA1: cdf459b2b6daa780613ff2991c18d1b88da32c56 SHA256: 9589f17c5b517a173dfd7bf7af24e114fe38e58269ddadd61348bf4ab9b09851 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: 18246 MD5sum: f69720f550371d31a9a99f60e9041a84 SHA1: 2d266951d95b88796ea073feb797c077c7a3c128 SHA256: 9054323168a4ad24cdc173bb428dd9e4ed3587823c397276377b094003a272f3 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: 63 Filename: ./all/perl-mro-compat_0.13-33.2_all.deb Size: 11030 MD5sum: b2f43bf1eb122df84ab0fe79bcc954a8 SHA1: 67ea82b6615aacc6b0e79857a696deb09ef559d7 SHA256: 7a13400f5a97eed6488ad4f560fb277b24731ed2fb38a2f345f182ed43d09437 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: 8170 MD5sum: e4a8cb49195ecbb1458092edc47c26a7 SHA1: 6802727a3f339036e84f778949cecec55cd37288 SHA256: 0f16b579dab934d75109bac5a3a94799d9509125d03d1235a72730b6b61e9402 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: 14954 MD5sum: bef2388372a2a1d84a5ef14a2ea7d744 SHA1: d9b3f97cba5aae206ac91e92e0627b2dd924777e SHA256: 9d8e59b832b6fb6f06ba58debbd33d3fc0b2b813ffb4907842331471db8486e0 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: 18912 MD5sum: a80b97f56853f203f23494c972af77e8 SHA1: a7c896530dbfb5d120c7bfdb590159b153aa7c6d SHA256: 230582cb43da02b1963e1e6ebf687e72ffb195a7dc4fd3b3ec53a02251e15837 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: 22016 MD5sum: d792deef1967a3078bbacb6ed5b8945c SHA1: 55144b7b8e3d5ef0c9496a125e9242d1f1d18eee SHA256: bfd1985f35f8df1b3728cfb8eefb74b49e48b76901711a274bd86fa4b058a94a 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: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: ./all/perl-test-class_0.52-29.2_all.deb Size: 56644 MD5sum: 714477d653fe2c5997b0bce1004645be SHA1: 99d89be4426c80513ef4a5b1e61183e6060274ca SHA256: fee333733346c26ba037042b399f611fc051927d09e8f1efffec4263d36ff362 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: 20290 MD5sum: 86a7500c17f0ea65b065a7b035b56588 SHA1: 4dc2cb5753257557d6d535ad970a40d6b68f82f1 SHA256: 0b1a705e3ed46e4b7d8496ad7da5d1f5207480144d29808dc7559757a2bc459e 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: 46956 MD5sum: 55ec19dcceede37c4cfed1d7722621ab SHA1: 30a202808e2f20dec77037e78a1c7cbfc0ef25f9 SHA256: 47d9510b33d70753ed0afc6a42f22b9e6a626c4f422cb4b66c00b574594f8ca1 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: 16850 MD5sum: 38bf42c48b6df96ea53d00a623624533 SHA1: fa64a015aee892e9930a74377ba803a9d3055767 SHA256: cfa805838d1f401990a7db02fa5d518a8458065a5742a0dfde33bad48bbd8820 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: 17836 MD5sum: 4d8222a47484e7a7a662f911282abb23 SHA1: dba966195963aa3081afbff69274ed75c4aecafc SHA256: 0e8eb99e8cfab5f5e21fe23fb71a46755744ad8d2c970599044edba905a122cc 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: 23094 MD5sum: 895deb20a15fc21319f54b65e8a9202e SHA1: b6d2b10159fd471f80e09e892bb373117f11b141 SHA256: 0270f965d750240a19321550bddd0544244e64e673199809e07c8ec405b35637 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: 13212 MD5sum: a2c154b6c65b84b8f58c14b6dc0c15ba SHA1: 2862ec48abd51289fbf7a2e2cdc1c3a2fa037a51 SHA256: 36d4562c9b301765227fc26a6dc256ca419e09c02b38bb80514a117a4e74c83a 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: 10666 MD5sum: 56f6c0a2110bb1163e3aba2586482001 SHA1: e78112c43fb0f11bf0eb429d9b6eaf44485651a8 SHA256: 8cc1ed04239fbda48c4812cdb4c87637072e913d917c0a0def2752d2bf4880e3 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: 14496 MD5sum: 5e9f3322d37eaa721083e6972d6cca32 SHA1: b4c04468cca5810d5650f5e1b2bae07e3152bd3b SHA256: 3c6163a6dbbbe0d6185a9ba5bca2452217bcbebb4238c400a221dea319b1df60 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: 33096 MD5sum: e190383d7e6f9bfb89b9068e9452cb75 SHA1: f60244c4c352b58811041c4fcd104650c58abf4a SHA256: b0eb06ac1597e40dbd72e78da9c6a2ab772a492af1633c4e20bdeeedabc2e445 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: 23148 MD5sum: 57282693f248bda20c10ac8a0714c5fe SHA1: 560f77365b33e60ae9bcd0741c23dd503f056f0b SHA256: 177106321dfb05f3a8dcdcf73b1324e380f89c7bb778c4b363ba10edd9204782 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: 7826 MD5sum: 695f1954a5bc9e0560bc00ae4cf622a9 SHA1: ff7556cc21590b0ab197f7ac450d1a7a06b96a0b SHA256: 52815ca2f0b95753cdc6c1ef52848d73666386335e5aaacda06fd0f039dd1c97 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: 290 Depends: libc6 Filename: ./amd64/perl-version_0.9928-27.2_amd64.deb Size: 88314 MD5sum: 29716bcbc4a943ae774a77888829d519 SHA1: c7c5f8c2b2e4d52f1876537bb2d9dec782232a20 SHA256: 49e76d099727f5ee6b3aa5a19a4ee55b7c27610bf9ea61daabb39071b111a035 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