Package: deb-perl-macros Version: 0.1-27.5 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 6 Depends: perl Filename: all/deb-perl-macros_0.1-27.5_all.deb Size: 2790 MD5sum: 18c4f6cb32b47e27d9cd590b970f1ba5 SHA1: c402209a411d983550aed452e54d6260d7de2bc1 SHA256: df160bea172d207bd109d000377f5c5f5c54eb39c2cb8c746e95fbc2b5996538 Priority: optional Homepage: https://build.opensuse.org/package/show/systemsmanagement:saltstack:bundle:debbuild/deb-perl-macros Description: Perl RPM macros for debbuild Perl RPM macros for debbuild Package: debbuild Version: 24.12.0-39.5 Architecture: all Maintainer: debbuild developers Installed-Size: 153 Depends: liblocale-gettext-perl,lsb-release,xz-utils,bash,bzip2,dpkg,dpkg-dev,fakeroot,gzip,patch,pax,perl Recommends: dpkg-sig,git-core,quilt,unzip,zip,zstd,debbuild-lua-support Suggests: rpm Filename: all/debbuild_24.12.0-39.5_all.deb Size: 55564 MD5sum: e47e48ec5feab88d9e41636e9e991e60 SHA1: 813f92e92c299140cd0e85db32b205f16413f4b8 SHA256: c3413d8bc3e913c86cd3eff396755333ec275693f5b590d313559f2aa2543a74 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Build Debian-compatible .deb packages from RPM .spec files debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files). It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully. Package: debbuild-lua-support Version: 24.12.0-39.5 Architecture: all Maintainer: debbuild developers Installed-Size: 8 Depends: debbuild (= 24.12.0-39.5),liblua-api-perl Filename: all/debbuild-lua-support_24.12.0-39.5_all.deb Size: 8352 MD5sum: b6dceba1048e161f6544fd67f97ca899 SHA1: 9364cdee5b0ba987c4c085b1bc9ecff4dc03b224 SHA256: e4188af73bfb3e1041bc39d1a4325e01186813e1828b5a6cceb66613efbb4ad3 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild Description: Lua macro support for debbuild This package adds the dependencies to support RPM macros written the Lua programming language. Package: debbuild-macros Version: 0.0.8-28.5 Architecture: all Maintainer: debbuild developers Installed-Size: 90 Depends: debbuild (>= 22.02.1) Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros Filename: all/debbuild-macros_0.0.8-28.5_all.deb Size: 26294 MD5sum: 885ceb74f8799c2a8d93931df5857481 SHA1: 82e1be636f2b6b79a21cb9223eaaa6532034093e SHA256: 1466b37b6fa031f8440bdba4da06d256ec1bfb76bf0ba7d8fbeb5d45dc588f61 Section: devel Priority: optional Homepage: https://github.com/debbuild/debbuild-macros Description: Various macros for extending debbuild functionality This package contains a set of RPM macros for debbuild, designed in such a manner that it is trivial to port RPM packaging to build Debian packages that are mostly in-line with Debian Policy. Package: liblua5-1-5 Version: 5.1.5-29.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-29.5) Provides: lua51-libs (= 5.1.5-29.5),liblua5-1 (= 5.1.5-29.5) Filename: amd64/liblua5-1-5_5.1.5-29.5_amd64.deb Size: 346930 MD5sum: 017758c6239b94d5d79b14f9bc8cc79f SHA1: 3960c7f6d88af92da3b0e231f6321b53f1f91972 SHA256: f1fedcd8d367e0185e1afcf5fb7fd323c7b7707c8535e7f28a6ed86a9b1a48d3 Section: System/Libraries Priority: optional Homepage: http://www.lua.org Description: The Lua integration library Lua is a programming language originally designed for extending applications, but is also frequently used as a general-purpose, stand-alone language. . Lua combines procedural syntax (similar to Pascal) with data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, interpreted from byte codes, and has automatic memory management, making it suitable for configuration, scripting, and rapid prototyping. Lua is implemented as a small library of C functions, written in ANSI C. Package: lua-macros Version: 20210827-25.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 1 Depends: pkg-config Filename: all/lua-macros_20210827-25.5_all.deb Size: 1530 MD5sum: 78f27f3addd5d05edaf72b86a987815d SHA1: 136efdfa33ab2275b01b9880e6e23d7f66387796 SHA256: b917e31e5cf1a351a426a6806c212c26a555530f1d397c6272eaf4e63c3c3d09 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-29.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1487 Depends: dpkg,libreadline8t64,libc6,libtinfo6 Provides: lua (= 5.1.5-29.5),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-29.5_amd64.deb Size: 426982 MD5sum: e569259c20375d5085df46ce578c4a16 SHA1: 7a267d7d9b27a40cd6ae830969a21a1b72011c55 SHA256: 474350dd90545a392e37580e9430ca15e1ed04e06b03a0d05d43aed672cd203c 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-29.5 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1699 Depends: liblua5-1-5 (= 5.1.5-29.5),lua51 (= 5.1.5-29.5),lua-macros,dpkg Provides: lua-devel (= 5.1.5-29.5),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-29.5) Filename: amd64/lua51-devel_5.1.5-29.5_amd64.deb Size: 443048 MD5sum: c8f093dae5c4dc78eec05cb846377eec SHA1: 386e3a6cdce538ecc67ae35af9e1ff38610d4ee2 SHA256: 928871b3ecfc9de07c1ad0521732d00b8d14c08f3a27101f745acfcda374d2eb 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-29.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 306 Filename: all/lua51-doc_5.1.5-29.5_all.deb Size: 73518 MD5sum: dcda665675c655eb61b0c93c76a6cb6f SHA1: 41dc7843d52a97a24540bdea0730c04e770e0334 SHA256: 9247a548e4197a624125e11384ae757676a1d9aa3fcf4ac6f78b5295568db512 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 77 Filename: all/perl-capture-tiny_0.48-27.5_all.deb Size: 30212 MD5sum: cb2b555b687df8d28fa5d817d69a4082 SHA1: 6b3102b0ba830931de397b4b73e6fd8bac6bb27c SHA256: ff16024a24311c7a24610daa523e689dba12d4b8dd3aecef4bd7ceb89ad443b6 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 48 Filename: all/perl-carp_1.50-27.5_all.deb Size: 22988 MD5sum: 96ee15681d53026e69b0217a7d9e8987 SHA1: 3053472e6d8183d8e3eb23c3bf70b8433fe47a09 SHA256: f874f9e2524453d5ca1370eaf59ccf30ac5b05035e3d00098c789610c529b678 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Carp/ Description: Alternative Warn and Die for Modules The Carp routines are useful in your own modules because they act like 'die()' or 'warn()', but with a message which is more likely to be useful to a user of your module. In the case of 'cluck()' and 'confess()', that context is a summary of every call in the call-stack; 'longmess()' returns the contents of the error message. . For a shorter message you can use 'carp()' or 'croak()' which report the error as being from where your module was called. 'shortmess()' returns the contents of this error message. There is no guarantee that that is where the error was, but it is a good educated guess. . 'Carp' takes care not to clobber the status variables '$!' and '$^E' in the course of assembling its error messages. This means that a '$SIG{__DIE__}' or '$SIG{__WARN__}' handler can capture the error information held in those variables, if it is required to augment the error message, and if the code calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee the latter. . You can also alter the way the output and logic of 'Carp' works, by changing some global variables in the 'Carp' namespace. See the section on 'GLOBAL VARIABLES' below. . Here is a more complete description of how 'carp' and 'croak' work. What they do is search the call-stack for a function call stack where they have not been told that there shouldn't be an error. If every call is marked safe, they give up and give a full stack backtrace instead. In other words they presume that the first likely looking potential suspect is guilty. Their rules for telling whether a call shouldn't generate errors work as follows: . * 1. . Any call from a package to itself is safe. . * 2. . Packages claim that there won't be errors on calls to or from packages explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is empty) '@ISA'. The ability to override what @ISA says is new in 5.8. . * 3. . The trust in item 2 is transitive. If A trusts B, and B trusts C, then A trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this trust relationship is identical to, "inherits from". . * 4. . Any call from an internal Perl module is safe. (Nothing keeps user modules from marking themselves as internal to Perl, but this practice is discouraged.) . * 5. . Any call to Perl's warning system (eg Carp itself) is safe. (This rule is what keeps it from reporting the error at the point where you call 'carp' or 'croak'.) . * 6. . '$Carp::CarpLevel' can be set to skip a fixed number of additional call levels. Using this is not recommended because it is very difficult to get it to behave correctly. Package: perl-class-data-inheritable Version: 0.09-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 11 Filename: all/perl-class-data-inheritable_0.09-27.5_all.deb Size: 6998 MD5sum: dd9dde85106272c09f87b62b4a40da3c SHA1: 7e97f963d7a95a647360b67f6773394dfe645efa SHA256: 594d96931da3ec4731d9ead9bd00ade313664435e0ffa19e732678116db255d1 Priority: optional Homepage: https://metacpan.org/release/Class-Data-Inheritable Description: Inheritable, overridable class data Class::Data::Inheritable is for creating accessor/mutators to class data. That is, if you want to store something about your class as a whole (instead of about a single object). This data is then inherited by your subclasses and can be overridden. . For example: . Pere::Ubu->mk_classdata('Suitcase'); . will generate the method Suitcase() in the class Pere::Ubu. . This new method can be used to get and set a piece of class data. . Pere::Ubu->Suitcase('Red'); $suitcase = Pere::Ubu->Suitcase; . The interesting part happens when a class inherits from Pere::Ubu: . package Raygun; use base qw(Pere::Ubu); . # Raygun's suitcase is Red. $suitcase = Raygun->Suitcase; . Raygun inherits its Suitcase class data from Pere::Ubu. . Inheritance of class data works analogous to method inheritance. As long as Raygun does not "override" its inherited class data (by using Suitcase() to set a new value) it will continue to use whatever is set in Pere::Ubu and inherit further changes: . # Both Raygun's and Pere::Ubu's suitcases are now Blue Pere::Ubu->Suitcase('Blue'); . However, should Raygun decide to set its own Suitcase() it has now "overridden" Pere::Ubu and is on its own, just like if it had overridden a method: . # Raygun has an orange suitcase, Pere::Ubu's is still Blue. Raygun->Suitcase('Orange'); . Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no longer effect Raygun. . # Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite. Pere::Ubu->Suitcase('Samsonite'); Package: perl-devel-stacktrace Version: 2.04-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 68 Filename: all/perl-devel-stacktrace_2.04-27.5_all.deb Size: 28330 MD5sum: c2c2f22f046ebf6dd299faa8924bbb65 SHA1: d4fedf18f44c20341dc70a55650010301d8f4d90 SHA256: 932c62042e25556be5e238358b1da5b82c16ea5cd3db1321bd529cbcf756ba39 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl Filename: all/perl-devel-symdump_2.18-27.5_all.deb Size: 14520 MD5sum: f2aa5cf917c38817bd0cb5ba4847e230 SHA1: 58c36191c5ac8ea4f986d592672635f22aacb992 SHA256: cc04f384feb29851e9bd150656c76afb58511248a52b33c228d8ca51aa312917 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Devel-Symdump/ Description: Dump Symbol Names or the Symbol Table This little package serves to access the symbol table of perl. Package: perl-exception-class Version: 1.45-27.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 97 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-27.9_all.deb Size: 38954 MD5sum: 2dc8e7d87673494ef6294bc30f137b7e SHA1: 4c4d372d25d7eaf9666ace3d80bce8885063c0ee SHA256: 8a4fc57e03abc4174e09526c9f70303e1c8175dcf521cabcd087faf563264fcc Priority: optional Homepage: https://metacpan.org/release/Exception-Class Description: Module that allows you to declare real exception classes in Perl *RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I highly recommend using Throwable instead of this module. . *RECOMMENDATION 2*: Whether or not you use Throwable, you should use Try::Tiny. . Exception::Class allows you to declare exception hierarchies in your modules in a "Java-esque" manner. . It features a simple interface allowing programmers to 'declare' exception classes at compile time. It also has a base exception class, Exception::Class::Base, that can be easily extended. . It is designed to make structured exception handling simpler and better by encouraging people to use hierarchies of exceptions in their applications, as opposed to a single catch-all exception class. . This module does not implement any try/catch syntax. Please see the "OTHER EXCEPTION MODULES (try/catch syntax)" section for more information on how to get this syntax. . You will also want to look at the documentation for Exception::Class::Base, which is the default base class for all exception objects created by this module. Package: perl-extutils-cbuilder Version: 0.280236-26.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 102 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-26.9_all.deb Size: 39272 MD5sum: 45fb725d2d103b6b4e6c7d9215477d1e SHA1: 5a471ff57d02deac60d815010a8cf48bd92e6c10 SHA256: f5967e98d81ef5b26fb7838de897d5bf4ed8338f1e2794153edb4441e2b8c947 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 21 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-27.5) Filename: all/perl-extutils-pkgconfig_1.160000-27.5_all.deb Size: 10468 MD5sum: 1e48063c408d0a70eb39edee8a13aef8 SHA1: b0b02fbf6a2a7fc66c669b66edf44e4347bb78f5 SHA256: 8a675a252664c7f3c6b1e2aa4c86ef866f024f9a44c2658877145c3ab077001e 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 67 Provides: libfile-path-perl (= 2.180000-27.5) Filename: all/perl-file-path_2.180000-27.5_all.deb Size: 30618 MD5sum: b16d2e9ef5faa9d73598101918816f3e SHA1: a6973c7b30dfef834bc899cebc65e00038dca55c SHA256: a8e694a2562b3fbbe784432385a32f527b7f4d09784f5f4b27cb10ef2e63f027 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-27.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 166 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-27.6_all.deb Size: 53822 MD5sum: 14327b358afd1a05ef65362eafdd1de3 SHA1: 8865e284c831f61c1af31f23485c25e7bd59fd82 SHA256: e4868e4b3f4b0dac21b94700f9784da4b569a631fd518c59097d8bfb178cc4ef 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-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl Filename: all/perl-ipc-cmd_1.04-27.5_all.deb Size: 33230 MD5sum: 3dd7210222001d49b86821b9b5b17c05 SHA1: 42cfd99ccac0abd215fc82ab0de44031c87c13a0 SHA256: 3c9d331bffccd3473d20c0b0a246c71b955d8c83be98c58873d04001f70758a3 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-module-metadata Version: 1.000038-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl Filename: all/perl-module-metadata_1.000038-27.5_all.deb Size: 30070 MD5sum: 20c8e8fcd78a01ee17e19478d3b15adc SHA1: c31d93a09d8a1f16f359c592f066e777e9874082 SHA256: 3d2da182d0f2657cd189530e64cd9f31a31278881cb980c4f9fad5cd2a2664bd 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-mro-compat Version: 0.15-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-mro-compat_0.15-27.5_all.deb Size: 17520 MD5sum: 5843c3bd1e14afc86b5a6f80cf61e532 SHA1: ab65bb13ab70db12c2287e79bd0e85155408b8e5 SHA256: 9fdeff05428039cf89d86b77270e97e99b39a7620e434e0ba88584c74c3a257e Priority: optional Homepage: https://metacpan.org/release/MRO-Compat Description: Mro::* interface compatibility for Perls < 5.9.5 The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. . This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). . It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. . If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. . Some parts of this code will work better and/or faster with Class::C3::XS installed (which is an optional prereq of Class::C3, which is in turn a prereq of this package), but it's not a requirement. . This module never exports any functions. All calls must be fully qualified with the 'mro::' prefix. . The interface documentation here serves only as a quick reference of what the function basically does, and what differences between MRO::Compat and 5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real interface docs, and contain a lot of other useful information. Package: perl-parent Version: 0.241-2.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-parent_0.241-2.5_all.deb Size: 8744 MD5sum: df9769170832bfffde9e5f96a6ab7178 SHA1: d27718266e79139582e50064eaa2945838b090e2 SHA256: 55483bdd1ea76e859a141bb287f83d0dc2d44cbd703ba385dbf6a64055a804e7 Section: Development/Libraries/Perl Priority: optional Homepage: https://metacpan.org/release/parent Description: Establish an ISA relationship with base classes at compile time Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. Mostly similar in effect to . package Baz; BEGIN { require Foo; require Bar; push @ISA, qw(Foo Bar); } . By default, every base class needs to live in a file of its own. If you want to have a subclass and its parent class in the same file, you can tell 'parent' not to load any modules by using the '-norequire' switch: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; use parent -norequire, 'Foo', 'Bar'; # will not go looking for Foo.pm or Bar.pm . This is equivalent to the following code: . package Foo; sub exclaim { "I CAN HAS PERL" } . package DoesNotLoadFooBar; push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar'; . This is also helpful for the case where a package lives within a differently named file: . package MyHash; use Tie::Hash; use parent -norequire, 'Tie::StdHash'; . This is equivalent to the following code: . package MyHash; require Tie::Hash; push @ISA, 'Tie::StdHash'; . If you want to load a subclass from a file that 'require' would not consider an eligible filename (that is, it does not end in either '.pm' or '.pmc'), use the following code: . package MySecondPlugin; require './plugins/custom.plugin'; # contains Plugin::Custom use parent -norequire, 'Plugin::Custom'; Package: perl-perl-ostype Version: 1.010-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 34 Filename: all/perl-perl-ostype_1.010-27.5_all.deb Size: 15496 MD5sum: 201b976b2013d736722555c322e65254 SHA1: e3843cc66a7743dcbacd4c8e1eaedb6191a81359 SHA256: cc31468301063c340b8fc4095bb5479aedce6eefae0e9f6224f22e8ed7a95f3d 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-29.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 32 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-29.8_all.deb Size: 18484 MD5sum: 0b4c23e79239e95fc11a6e13d7bbc5c3 SHA1: edb75d982d6739b4c5799512479eb321c6f244d5 SHA256: 7067d9a5f441b1610151d016cb51668f4e320acd7443d18d4872da49167da111 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-test-differences Version: 0.710.0-27.9 Architecture: all Maintainer: Uyuni packagers Installed-Size: 33 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-27.9) Filename: all/perl-test-differences_0.710.0-27.9_all.deb Size: 18554 MD5sum: 21947ad40cfd62049e7bdb04264ce69b SHA1: 3fe653967d1b7d623af0f23abded3594dfee9f38 SHA256: c4b944778dc9ca2a3b1cc12d05b50ebe9263579be10994bc2ac6640975f8632b Priority: optional Homepage: https://metacpan.org/release/Test-Differences Description: Test strings and data structures and show differences if not ok When the code you're testing returns multiple lines, records or data structures and they're just plain wrong, an equivalent to the Unix 'diff' utility may be just what's needed. Here's output from an example test script that checks two text documents and then two (trivial) data structures: . t/99example....1..3 not ok 1 - differences in text # Failed test ((eval 2) at line 14) # +---+----------------+----------------+ # | Ln|Got |Expected | # +---+----------------+----------------+ # | 1|this is line 1 |this is line 1 | # * 2|this is line 2 |this is line b * # | 3|this is line 3 |this is line 3 | # +---+----------------+----------------+ not ok 2 - differences in whitespace # Failed test ((eval 2) at line 20) # +---+------------------+------------------+ # | Ln|Got |Expected | # +---+------------------+------------------+ # | 1| indented | indented | # * 2| indented |\tindented * # | 3| indented | indented | # +---+------------------+------------------+ not ok 3 # Failed test ((eval 2) at line 22) # +----+-------------------------------------+----------------------------+ # | Elt|Got |Expected | # +----+-------------------------------------+----------------------------+ # * 0|bless( [ |[ * # * 1| 'Move along, nothing to see here' | 'Dry, humorless message' * # * 2|], 'Test::Builder' ) |] * # +----+-------------------------------------+----------------------------+ # Looks like you failed 3 tests of 3. . eq_or_diff_...() compares two strings or (limited) data structures and either emits an ok indication or a side-by-side diff. Test::Differences is designed to be used with Test.pm and with Test::Simple, Test::More, and other Test::Builder based testing modules. As the SYNOPSIS shows, another testing module must be used as the basis for your test suite. Package: perl-test-pod Version: 1.52-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 22 Depends: perl Filename: all/perl-test-pod_1.52-27.5_all.deb Size: 13380 MD5sum: 598b92f10732797f0f9ce577b7df6a30 SHA1: cefc9b41f114749e0a32992482091522a93054a6 SHA256: 4d0ebb960207b76e974fe43501219dfa18ac96255df6c88d8d00b51269219ae5 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-28.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 16 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-28.12_all.deb Size: 10800 MD5sum: 3aa5bd5e68a9485da07bd11b6f5a138b SHA1: 0fb08c74d0b498f6b9c6b6062c022b89ff994a3a SHA256: cfa8b6f6d4de374ef01ce27eb9062f1e2dd25da71810a82e5c342fc63a0afc76 Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/ Description: Check for pod coverage in your distribution. Test::Pod::Coverage is used to create a test for your distribution, to ensure that all relevant files in your distribution are appropriately documented in pod. . Can also be called with the Pod::Coverage manpage parms. . use Test::Pod::Coverage tests=>1; pod_coverage_ok( "Foo::Bar", { also_private => [ qr/^[A-Z_]+$/ ], }, "Foo::Bar, with all-caps functions as privates", ); . The the Pod::Coverage manpage parms are also useful for subclasses that don't re-document the parent class's methods. Here's an example from the Mail::SRS manpage. . pod_coverage_ok( "Mail::SRS" ); # No exceptions . # Define the three overridden methods. my $trustme = { trustme => [qr/^(new|parse|compile)$/] }; pod_coverage_ok( "Mail::SRS::DB", $trustme ); pod_coverage_ok( "Mail::SRS::Guarded", $trustme ); pod_coverage_ok( "Mail::SRS::Reversable", $trustme ); pod_coverage_ok( "Mail::SRS::Shortcut", $trustme ); . Alternately, you could use the Pod::Coverage::CountParents manpage, which always allows a subclass to reimplement its parents' methods without redocumenting them. For example: . my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' }; pod_coverage_ok( "IO::Handle::Frayed", $trustparents ); . (The 'coverage_class' parameter is not passed to the coverage class with other parameters.) . If you want POD coverage for your module, but don't want to make Test::Pod::Coverage a prerequisite for installing, create the following as your _t/pod-coverage.t_ file: . use Test::More; eval "use Test::Pod::Coverage"; plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@; . plan tests => 1; pod_coverage_ok( "Pod::Master::Html"); . Finally, Module authors can include the following in a _t/pod-coverage.t_ file and have 'Test::Pod::Coverage' automatically find and check all modules in the module distribution: . use Test::More; eval "use Test::Pod::Coverage 1.00"; plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@; all_pod_coverage_ok(); Package: perl-text-diff Version: 1.45-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 84 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-27.5_all.deb Size: 32924 MD5sum: 55758baf266f15b4a181fa50e2ce1f7c SHA1: ab7a32b375772d743f729f38496843a7e45f1c6a SHA256: 293d20e3b27b27ee6140e9d2d17a58b399962663fc6241172482f7be3dff7c6a Section: Development/Libraries/Perl Priority: optional Homepage: http://search.cpan.org/dist/Text-Diff/ Description: Perform diffs on files and record sets 'diff()' provides a basic set of services akin to the GNU 'diff' utility. It is not anywhere near as feature complete as GNU 'diff', but it is better integrated with Perl and available on all platforms. It is often faster than shelling out to a system's 'diff' executable for small files, and generally slower on larger files. . Relies on Algorithm::Diff for, well, the algorithm. This may not produce the same exact diff as a system's local 'diff' executable, but it will be a valid diff and comprehensible by 'patch'. We haven't seen any differences between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined them to make sure they are indeed identical. . *Note*: If you don't want to import the 'diff' function, do one of the following: . use Text::Diff (); . require Text::Diff; . That's a pretty rare occurrence, so 'diff()' is exported by default. . If you pass a filename, but the file can't be read, then 'diff()' will 'croak'. Package: perl-try-tiny Version: 0.31-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 40 Filename: all/perl-try-tiny_0.31-27.5_all.deb Size: 24308 MD5sum: ade251c5535dce94fd8ce98745609838 SHA1: b7a9b96a6d77994b21606207b07961b91750182d SHA256: 52d6740da7395e9ec322aa23e773a7367103303877cdd650fe28407a64222b02 Priority: optional Homepage: https://metacpan.org/release/Try-Tiny Description: Minimal try/catch with proper preservation of $@ This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. . This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. . The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. . It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). . If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': . my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; . my $x = eval { die "foo" } || "bar"; . You can add 'finally' blocks, yielding the following: . my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; . 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. . Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this. Package: perl-universal-require Version: 0.19-27.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 12 Filename: all/perl-universal-require_0.19-27.5_all.deb Size: 8702 MD5sum: ec7b8802a1abbcc76f6f089ef6fe6ee1 SHA1: 9e1c722dde04dd44f26510f2169ed8b2b748ca5b SHA256: 19f1002e238c547191f2754f18abca03df37ad01cc711699e712fbcd2f2e70d9 Priority: optional Homepage: https://metacpan.org/release/UNIVERSAL-require Description: Require() modules from a variable [deprecated] Before using this module, you should look at the alternatives, some of which are listed in SEE ALSO below. . This module provides a safe mechanism for loading a module at runtime, when you have the name of the module in a variable. . If you've ever had to do this... . eval "require $module"; . to get around the bareword caveats on require(), this module is for you. It creates a universal require() class method that will work with every Perl module and its secure. So instead of doing some arcane eval() work, you can do this: . $module->require; . It doesn't save you much typing, but it'll make a lot more sense to someone who's not a ninth level Perl acolyte.