Package: deb-perl-macros
Version: 0.1-2.16
Architecture: all
Maintainer: Victor Zhestkov <vzhestkov@suse.com>
Installed-Size: 42
Depends: perl
Filename: all/deb-perl-macros_0.1-2.16_all.deb
Size: 2696
MD5sum: 7cbe2c976140771204eeff81975ad0ba
SHA1: dc4d09876dec96eb7cf230702cc0c276fdde27d0
SHA256: 7367716ef0b5866b7ec5f944f801b67a13be716f21f8fb0ed46f669fc43aa9d2
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-3.6
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
Installed-Size: 209
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-3.6_all.deb
Size: 55160
MD5sum: beae7725d1b121f4fc8dfd68b3389961
SHA1: ca69b44ab8735023d8f86eea6853c57a8115db8f
SHA256: 3b5bd2711464d72b991da84254e76b205f1705b0b19cd0b26c7c5a5c7dd10a3f
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-3.6
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
Installed-Size: 32
Depends: debbuild (= 24.12.0-3.6),liblua-api-perl
Filename: all/debbuild-lua-support_24.12.0-3.6_all.deb
Size: 8624
MD5sum: e5d2630966aa87ffe3201ce145c1ceed
SHA1: 37c650706c742dde1613224792fb5bbfd8f4f99d
SHA256: de6b60866e0947cc70ed1488015dde7a4e24a8107c2e2ee4ecefde373f37c2b1
Section: devel
Priority: optional
Homepage: https://github.com/debbuild/debbuild
Description: Lua macro support for debbuild
This package adds the dependencies to support RPM macros
written the Lua programming language.
Package: debbuild-macros
Version: 0.0.7-2.1
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
Installed-Size: 126
Depends: debbuild (>= 22.02.1)
Provides: debbuild-macros-debpkg,debbuild-macros-cmake,cmake-deb-macros,debbuild-macros-mga-mkrel,debbuild-macros-mga-mklibname,mga-deb-macros,debbuild-macros-python,debbuild-macros-python2,debbuild-macros-python3,python-deb-macros,python2-deb-macros,python3-deb-macros,debbuild-macros-perl,perl-deb-macros,debbuild-macros-ruby,ruby-deb-macros,debbuild-macros-golang,go-deb-macros,golang-deb-macros,debbuild-macros-apache2,apache2-deb-macros,debbuild-macros-gpgverify,debbuild-macros-vpath,debbuild-macros-ninja,ninja-deb-macros,debbuild-macros-meson,meson-deb-macros,debbuild-macros-apparmor,apparmor-deb-macros,debbuild-macros-firewalld,firewalld-deb-macros,debbuild-macros-systemd,systemd-deb-macros
Filename: all/debbuild-macros_0.0.7-2.1_all.deb
Size: 25492
MD5sum: 3da27f672ba731f5c5b065c1ca2356ff
SHA1: bf0a151f649219068aa70929d10daf91cc4b8cfd
SHA256: 792924dddf5741241c069f750d138e2156f80739af6f489a8f9b1fbd0d03fa31
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-31.7
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 870
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-31.7)
Provides: lua51-libs (= 5.1.5-31.7),liblua5-1 (= 5.1.5-31.7)
Filename: armhf/liblua5-1-5_5.1.5-31.7_armhf.deb
Size: 272392
MD5sum: 24946ea8591bafd8b9db2d105205d599
SHA1: f5035d4f5656f39127047835f6096e3f5907ab6b
SHA256: 19d5f01c6bd63c6e07d0dc17527e56719b41e1d34d14e1945b45b17da23694da
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-26.1
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 25
Filename: all/lua-macros_20210827-26.1_all.deb
Size: 1572
MD5sum: f3aeb9ba7ea9888c5d807e8b697e8091
SHA1: 2a248c9ccb0e57d7bda9a77a88407fd9789829c6
SHA256: 45d87103d803454b2c37ebc7b8c32793229c93d1bd916b43f587bb4c3c6694c4
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-31.7
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1541
Depends: dpkg,libc6,libreadline8,libtinfo6
Provides: lua (= 5.1.5-31.7),lua-api (= 5.1)
Filename: armhf/lua51_5.1.5-31.7_armhf.deb
Size: 333472
MD5sum: 77608c4c89b09b92ad30aa16c43483a7
SHA1: 26edf4bd362a70608fcbd3be5dfee89385478f89
SHA256: a1cad5d1202e143c3849ea6c425d63a5fe1b8dcec10b71a37bda622c155c7885
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-31.7
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1235
Depends: liblua5-1-5 (= 5.1.5-31.7),lua51 (= 5.1.5-31.7),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-31.7),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-31.7)
Filename: armhf/lua51-devel_5.1.5-31.7_armhf.deb
Size: 351800
MD5sum: 272560473f9d32ae081e1d4691f3d242
SHA1: 533394abf3de74b26f375e524c16daa043077676
SHA256: 112370a0dfeb93bbd0e17b933838e39e2d1f1aebf28a372e989f71eb8e692b8b
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-31.7
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 330
Filename: all/lua51-doc_5.1.5-31.7_all.deb
Size: 71660
MD5sum: 89adf8a4b8b86b2d10858668fe954fc3
SHA1: 8e25ba7f568c844cf5f96858753fa730eadfe6d0
SHA256: d2a3589f65c253a4efc5efe3a57d0bb25e9390cfc9f23dda8e33beb60b623b9b
Section: Documentation/HTML
Priority: optional
Homepage: http://www.lua.org
Description: Documentation for Lua, a small embeddable language
Lua is a programming language originally designed for extending
applications, but is also frequently used as a general-purpose,
stand-alone language.
.
Lua combines procedural syntax (similar to Pascal) with
data description constructs based on associative arrays and extensible
semantics. Lua is dynamically typed, interpreted from byte codes, and
has automatic memory management, making it suitable for configuration,
scripting, and rapid prototyping. Lua is implemented as a small library
of C functions, written in ANSI C.
Package: perl-capture-tiny
Version: 0.48-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 121
Filename: all/perl-capture-tiny_0.48-3.15_all.deb
Size: 30004
MD5sum: 684a86aba747acc26611662435921b23
SHA1: ec00c60fecd383e6d9257d84f61cbf30f27a8541
SHA256: 496ba7f676bb9b7a9620212eec196b7e9c42f1aadde57feaa60531a8c1d52218
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Capture-Tiny/
Description: Capture STDOUT and STDERR from Perl, XS or external programs
Capture::Tiny provides a simple, portable way to capture almost anything
sent to STDOUT or STDERR, regardless of whether it comes from Perl, from XS
code or from an external program. Optionally, output can be teed so that it
is captured while being passed through to the original filehandles. Yes, it
even works on Windows (usually). Stop guessing which of a dozen capturing
modules to use in any particular situation and just use this one.
Package: perl-carp
Version: 1.50-3.18
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 88
Filename: all/perl-carp_1.50-3.18_all.deb
Size: 22676
MD5sum: 3155b2f3ce6705142b3eb1f8917a3806
SHA1: 68ad1f6cd26e02bf61e45acc68a3dda9e6d09ad5
SHA256: 910623f16c73499aeb688ae999790867b5c75ba8a60e6add1cf8599c3f30a3c7
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Carp/
Description: Alternative Warn and Die for Modules
The Carp routines are useful in your own modules because they act like
'die()' or 'warn()', but with a message which is more likely to be useful
to a user of your module. In the case of 'cluck()' and 'confess()', that
context is a summary of every call in the call-stack; 'longmess()' returns
the contents of the error message.
.
For a shorter message you can use 'carp()' or 'croak()' which report the
error as being from where your module was called. 'shortmess()' returns the
contents of this error message. There is no guarantee that that is where
the error was, but it is a good educated guess.
.
'Carp' takes care not to clobber the status variables '$!' and '$^E' in the
course of assembling its error messages. This means that a '$SIG{__DIE__}'
or '$SIG{__WARN__}' handler can capture the error information held in those
variables, if it is required to augment the error message, and if the code
calling 'Carp' left useful values there. Of course, 'Carp' can't guarantee
the latter.
.
You can also alter the way the output and logic of 'Carp' works, by
changing some global variables in the 'Carp' namespace. See the section on
'GLOBAL VARIABLES' below.
.
Here is a more complete description of how 'carp' and 'croak' work. What
they do is search the call-stack for a function call stack where they have
not been told that there shouldn't be an error. If every call is marked
safe, they give up and give a full stack backtrace instead. In other words
they presume that the first likely looking potential suspect is guilty.
Their rules for telling whether a call shouldn't generate errors work as
follows:
.
* 1.
.
Any call from a package to itself is safe.
.
* 2.
.
Packages claim that there won't be errors on calls to or from packages
explicitly marked as safe by inclusion in '@CARP_NOT', or (if that array is
empty) '@ISA'. The ability to override what @ISA says is new in 5.8.
.
* 3.
.
The trust in item 2 is transitive. If A trusts B, and B trusts C, then A
trusts C. So if you do not override '@ISA' with '@CARP_NOT', then this
trust relationship is identical to, "inherits from".
.
* 4.
.
Any call from an internal Perl module is safe. (Nothing keeps user modules
from marking themselves as internal to Perl, but this practice is
discouraged.)
.
* 5.
.
Any call to Perl's warning system (eg Carp itself) is safe. (This rule is
what keeps it from reporting the error at the point where you call 'carp'
or 'croak'.)
.
* 6.
.
'$Carp::CarpLevel' can be set to skip a fixed number of additional call
levels. Using this is not recommended because it is very difficult to get
it to behave correctly.
Package: perl-class-data-inheritable
Version: 0.09-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 55
Filename: all/perl-class-data-inheritable_0.09-3.15_all.deb
Size: 7228
MD5sum: bc977a9c41a6a7203cc735f41e03fe1c
SHA1: 0d61c8a9fca8993ed9c830a02085af20ec27c413
SHA256: f45fb1447988f97064402f567d64cdc6f8788a9d7f0478686f323523b95fb2bc
Priority: optional
Homepage: https://metacpan.org/release/Class-Data-Inheritable
Description: Inheritable, overridable class data
Class::Data::Inheritable is for creating accessor/mutators to class data.
That is, if you want to store something about your class as a whole
(instead of about a single object). This data is then inherited by your
subclasses and can be overridden.
.
For example:
.
Pere::Ubu->mk_classdata('Suitcase');
.
will generate the method Suitcase() in the class Pere::Ubu.
.
This new method can be used to get and set a piece of class data.
.
Pere::Ubu->Suitcase('Red');
$suitcase = Pere::Ubu->Suitcase;
.
The interesting part happens when a class inherits from Pere::Ubu:
.
package Raygun;
use base qw(Pere::Ubu);
.
# Raygun's suitcase is Red.
$suitcase = Raygun->Suitcase;
.
Raygun inherits its Suitcase class data from Pere::Ubu.
.
Inheritance of class data works analogous to method inheritance. As long as
Raygun does not "override" its inherited class data (by using Suitcase() to
set a new value) it will continue to use whatever is set in Pere::Ubu and
inherit further changes:
.
# Both Raygun's and Pere::Ubu's suitcases are now Blue
Pere::Ubu->Suitcase('Blue');
.
However, should Raygun decide to set its own Suitcase() it has now
"overridden" Pere::Ubu and is on its own, just like if it had overridden a
method:
.
# Raygun has an orange suitcase, Pere::Ubu's is still Blue.
Raygun->Suitcase('Orange');
.
Now that Raygun has overridden Pere::Ubu further changes by Pere::Ubu no
longer effect Raygun.
.
# Raygun still has an orange suitcase, but Pere::Ubu is using Samsonite.
Pere::Ubu->Suitcase('Samsonite');
Package: perl-devel-stacktrace
Version: 2.04-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 113
Filename: all/perl-devel-stacktrace_2.04-3.15_all.deb
Size: 28408
MD5sum: 98676cad8d710ceeb334509c4c828cad
SHA1: bc5844c525438de3e34284048cbd4e378c8de554
SHA256: e62ea493e5eedd4bac6d0043c97069b07d9aa09a0219813806d3499ae55761c1
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/Devel-StackTrace
Description: An object representing a stack trace
The 'Devel::StackTrace' module contains two classes, 'Devel::StackTrace'
and Devel::StackTrace::Frame. These objects encapsulate the information
that can retrieved via Perl's 'caller' function, as well as providing a
simple interface to this data.
.
The 'Devel::StackTrace' object contains a set of 'Devel::StackTrace::Frame'
objects, one for each level of the stack. The frames contain all the data
available from 'caller'.
.
This code was created to support my Exception::Class::Base class (part of
Exception::Class) but may be useful in other contexts.
Package: perl-devel-symdump
Version: 2.18-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 76
Depends: perl
Filename: all/perl-devel-symdump_2.18-3.15_all.deb
Size: 14368
MD5sum: 56b5d4ac9edb889b1bb4f8a0cf349810
SHA1: fa7435eeab4698a0c76a21bc893cbb3d2d3d3c3a
SHA256: 5f0c4474aa5decadad80f33b939098a195c03c209f11145170b76bacf7473adf
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Devel-Symdump/
Description: Dump Symbol Names or the Symbol Table
This little package serves to access the symbol table of perl.
Package: perl-exception-class
Version: 1.45-3.25
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 142
Depends: perl-class-data-inheritable,perl-devel-stacktrace
Filename: all/perl-exception-class_1.45-3.25_all.deb
Size: 39068
MD5sum: f3e2d5524ba0484bbd133e4a7f9f6d1e
SHA1: 31b383b3033040d9376f6ad5d1c6f59f612b98e4
SHA256: 15d533c550ac31313a44e9c9c2a75fabb7c44e83cdc81cd503ac1b5e345f33f1
Priority: optional
Homepage: https://metacpan.org/release/Exception-Class
Description: Module that allows you to declare real exception classes in Perl
*RECOMMENDATION 1*: If you are writing modern Perl code with Moose or Moo I
highly recommend using Throwable instead of this module.
.
*RECOMMENDATION 2*: Whether or not you use Throwable, you should use
Try::Tiny.
.
Exception::Class allows you to declare exception hierarchies in your
modules in a "Java-esque" manner.
.
It features a simple interface allowing programmers to 'declare' exception
classes at compile time. It also has a base exception class,
Exception::Class::Base, that can be easily extended.
.
It is designed to make structured exception handling simpler and better by
encouraging people to use hierarchies of exceptions in their applications,
as opposed to a single catch-all exception class.
.
This module does not implement any try/catch syntax. Please see the "OTHER
EXCEPTION MODULES (try/catch syntax)" section for more information on how
to get this syntax.
.
You will also want to look at the documentation for Exception::Class::Base,
which is the default base class for all exception objects created by this
module.
Package: perl-extutils-cbuilder
Version: 0.280236-2.35
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 155
Depends: perl,perl-ipc-cmd,perl-perl-ostype
Filename: all/perl-extutils-cbuilder_0.280236-2.35_all.deb
Size: 39236
MD5sum: d953315a66fcce1ce19d4d129c61f223
SHA1: 76a76118161ccd2048ff7418eec8b532ab9eb45f
SHA256: 7a72c0903fd869e998ed4cd0f697f800c226d805674b6bf1d7a82da277329d9f
Priority: optional
Homepage: https://metacpan.org/release/ExtUtils-CBuilder
Description: Compile and link C code for Perl modules
This module can build the C portions of Perl modules by invoking the
appropriate compilers and linkers in a cross-platform manner. It was
motivated by the 'Module::Build' project, but may be useful for other
purposes as well. However, it is _not_ intended as a general cross-platform
interface to all your C building needs. That would have been a much more
ambitious goal!
Package: perl-extutils-makemaker
Version: 7.66-4.18
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 890
Filename: all/perl-extutils-makemaker_7.66-4.18_all.deb
Size: 304200
MD5sum: 52459385749e86f4a2fb120c1bc39270
SHA1: a2a9f9586783dbc6c39e580dd8edf972b7d6bc4a
SHA256: 35bf28a078f3341c33f165eadab6e69f822ac3ba65cec562dd91bedd602dd55f
Priority: optional
Homepage: https://metacpan.org/release/ExtUtils-MakeMaker
Description: Create a module Makefile
This utility is designed to write a Makefile for an extension module from a
Makefile.PL. It is based on the Makefile.SH model provided by Andy
Dougherty and the perl5-porters.
.
It splits the task of generating the Makefile into several subroutines that
can be individually overridden. Each subroutine returns the text it wishes
to have written to the Makefile.
.
As there are various Make programs with incompatible syntax, which use
operating system shells, again with incompatible syntax, it is important
for users of this module to know which flavour of Make a Makefile has been
written for so they'll use the correct one and won't have to face the
possibly bewildering errors resulting from using the wrong one.
.
On POSIX systems, that program will likely be GNU Make; on Microsoft
Windows, it will be either Microsoft NMake, DMake or GNU Make. See the
section on the L</"MAKE"> parameter for details.
.
ExtUtils::MakeMaker (EUMM) is object oriented. Each directory below the
current directory that contains a Makefile.PL is treated as a separate
object. This makes it possible to write an unlimited number of Makefiles
with a single invocation of WriteMakefile().
.
All inputs to WriteMakefile are Unicode characters, not just octets. EUMM
seeks to handle all of these correctly. It is currently still not possible
to portably use Unicode characters in module names, because this requires
Perl to handle Unicode filenames, which is not yet the case on Windows.
.
See L<ExtUtils::MakeMaker::FAQ> for details of the design and usage.
Package: perl-extutils-pkgconfig
Version: 1.160000-3.20
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 61
Depends: pkg-config
Provides: libextutils-pkgconfig-perl (= 1.160000-3.20)
Filename: all/perl-extutils-pkgconfig_1.160000-3.20_all.deb
Size: 10556
MD5sum: 15c761394af577b96f6606efc6e28b59
SHA1: 606608f118fc52b6b859f185732f5176e9eb6e86
SHA256: 22c189afdeb9ada7eba52fe49e544bf032e559661b7ac9d00de0e6329692830b
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/ExtUtils-PkgConfig/
Description: Simplistic Interface to Pkg-Config
The pkg-config program retrieves information about installed libraries,
usually for the purposes of compiling against and linking to them.
.
ExtUtils::PkgConfig is a very simplistic interface to this utility,
intended for use in the Makefile.PL of perl extensions which bind libraries
that pkg-config knows. It is really just boilerplate code that you would've
written yourself.
Package: perl-file-path
Version: 2.180000-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 107
Provides: libfile-path-perl (= 2.180000-3.15)
Filename: all/perl-file-path_2.180000-3.15_all.deb
Size: 30672
MD5sum: adf512144174e3445ff7d963919d1ad3
SHA1: d1cc3798eb7474ec1aa096d11d0cd96ea68df470
SHA256: 6672de217485fe82b0ab90a9eee0258ecf3141ddb0cfb102a028cde087019e24
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/File-Path
Description: Create or remove directory trees
This module provides a convenient way to create directories of arbitrary
depth and to delete an entire directory subtree from the filesystem.
Package: perl-file-temp
Version: 0.2311-3.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 207
Depends: perl-file-path,perl-parent
Filename: all/perl-file-temp_0.2311-3.16_all.deb
Size: 53300
MD5sum: a14c2aedd24b0f8367fecabdd5e7ad4b
SHA1: 5b875387d7aba975ecf595e5ae591b47770ad193
SHA256: a5f84156634665da61e29a243bc373025f0892e3952d3f745b3e91beae048013
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/File-Temp
Description: Return name and handle of a temporary file safely
'File::Temp' can be used to create and open temporary files in a safe way.
There is both a function interface and an object-oriented interface. The
File::Temp constructor or the tempfile() function can be used to return the
name and the open filehandle of a temporary file. The tempdir() function
can be used to create a temporary directory.
.
The security aspect of temporary file creation is emphasized such that a
filehandle and filename are returned together. This helps guarantee that a
race condition can not occur where the temporary file is created by another
process between checking for the existence of the file and its opening.
Additional security levels are provided to check, for example, that the
sticky bit is set on world writable directories. See "safe_level" for more
information.
.
For compatibility with popular C library functions, Perl implementations of
the mkstemp() family of functions are provided. These are, mkstemp(),
mkstemps(), mkdtemp() and mktemp().
.
Additionally, implementations of the standard POSIX tmpnam() and tmpfile()
functions are provided if required.
.
Implementations of mktemp(), tmpnam(), and tempnam() are provided, but
should be used with caution since they return only a filename that was
valid when function was called, so cannot guarantee that the file will not
exist by the time the caller opens the filename.
.
Filehandles returned by these functions support the seekable methods.
Package: perl-ipc-cmd
Version: 1.04-3.18
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 127
Depends: perl
Filename: all/perl-ipc-cmd_1.04-3.18_all.deb
Size: 33160
MD5sum: 54a9bb72dc1aae885b8f7936c07cb7b3
SHA1: 164868bca064887c4a4576c49d272b1cc39bb1c8
SHA256: 46316260f4c17ab293d6a72cfb832e146fe50bf1f8d6ae0deb27128180644501
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/IPC-Cmd
Description: Finding and running system commands made easy
IPC::Cmd allows you to run commands platform independently, interactively
if desired, but have them still work.
.
The 'can_run' function can tell you if a certain binary is installed and if
so where, whereas the 'run' function can actually execute any of the
commands you give it and give you a clear return value, as well as adhere
to your verbosity settings.
Package: perl-lua-api
Version: 0.04-2.93
Architecture: armhf
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 714
Depends: perl-base,liblua5-1-5,libc6
Filename: armhf/perl-lua-api_0.04-2.93_armhf.deb
Size: 166740
MD5sum: 60c07a7664eb7668c91d7ceff14439c1
SHA1: b70091c67c038df67b1fa30f7cc2d27d57d7737a
SHA256: 4cad07230b64692d749ef4f9498cd0890592a8dc50fbaed60b83e84f007f577b
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/Lua-API
Description: Interface to Lua's embedding API
*Lua* is a simple, expressive, extension programming language that is
easily embeddable. *Lua::API* provides Perl bindings to Lua's C-based
embedding API. It allows Perl routines to be called from Lua as if they
were written in C, and allows Perl routines to directly manipulate the Lua
interpreter and its environment. It presents a very low-level interface
(essentially equivalent to the C interface), so is aimed at developers who
need that sort of access.
.
*Lua::API* is not the first place to turn to if you need a simple, more
Perl-ish interface; for that, try *Inline::Lua*, which takes a much higher
level approach and masks most of the underlying complexity in communicating
between Lua and Perl. Unfortunately by hiding the complexity, this approach
also prevents full operability. For *Inline::Lua* this is a necessary
tradeoff, but it does mean that you cannot create as tight an integration
with Lua.
Package: perl-module-build
Version: 0.423400-4.38
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 733
Depends: perl,perl-extutils-cbuilder,perl-base,perl-module-metadata,perl-perl-ostype
Recommends: libextutils-manifest-perl (>= 1.54)
Provides: libmodule-build-perl (= 0.423400-4.38)
Filename: all/perl-module-build_0.423400-4.38_all.deb
Size: 251604
MD5sum: 676cdac3415c0b82110100c175d8841f
SHA1: a7ecfac4fb59c275ec81dc984981e166986368d0
SHA256: 47953d46c012eef8cf1559a98121219dd0655a911535c99654f67b8d598249a2
Priority: optional
Homepage: https://metacpan.org/release/Module-Build
Description: Build and install Perl modules
'Module::Build' is a system for building, testing, and installing Perl
modules. It is meant to be an alternative to 'ExtUtils::MakeMaker'.
Developers may alter the behavior of the module through subclassing. It
also does not require a 'make' on your system - most of the 'Module::Build'
code is pure-perl and written in a very cross-platform way.
.
See "COMPARISON" for more comparisons between 'Module::Build' and other
installer tools.
.
To install 'Module::Build', and any other module that uses 'Module::Build'
for its installation process, do the following:
.
perl Build.PL # 'Build.PL' script creates the 'Build' script
./Build # Need ./ to ensure we're using this "Build" script
./Build test # and not another one that happens to be in the PATH
./Build install
.
This illustrates initial configuration and the running of three 'actions'.
In this case the actions run are 'build' (the default action), 'test', and
'install'. Other actions defined so far include:
.
build manifest
clean manifest_skip
code manpages
config_data pardist
diff ppd
dist ppmdist
distcheck prereq_data
distclean prereq_report
distdir pure_install
distinstall realclean
distmeta retest
distsign skipcheck
disttest test
docs testall
fakeinstall testcover
help testdb
html testpod
install testpodcoverage
installdeps versioninstall
.
You can run the 'help' action for a complete list of actions.
Package: perl-module-metadata
Version: 1.000038-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 111
Depends: perl
Filename: all/perl-module-metadata_1.000038-3.15_all.deb
Size: 29644
MD5sum: c36d48f8ee17d1a3b0c7de07729fd648
SHA1: 5b0eed6d5ce0d8e58696b7d2b3317ba1240dca1b
SHA256: 2b1311d2dfdcec992ac30e6260100332dde99fc421ce2d40221b6f45cf176119
Priority: optional
Homepage: https://metacpan.org/release/Module-Metadata
Description: Gather package and POD information from perl module files
This module provides a standard way to gather metadata about a .pm file
through (mostly) static analysis and (some) code execution. When
determining the version of a module, the '$VERSION' assignment is 'eval'ed,
as is traditional in the CPAN toolchain.
Package: perl-module-runtime
Version: 0.016-3.48
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-module-runtime_0.016-3.48_all.deb
Size: 18440
MD5sum: eb0fdefbfd5e227cb30f2f66aaf11925
SHA1: 6304f0a07d7fdc343be013a06d3f2d5486c1cb1f
SHA256: 9f3ddb997a4a8d2f7078ce367a673b657d49dbdc165b1ec275d2140b4c654848
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Module-Runtime/
Description: Runtime Module Handling
The functions exported by this module deal with runtime handling of Perl
modules, which are normally handled at compile time. This module avoids
using any other modules, so that it can be used in low-level
infrastructure.
.
The parts of this module that work with module names apply the same syntax
that is used for barewords in Perl source. In principle this syntax can
vary between versions of Perl, and this module applies the syntax of the
Perl on which it is running. In practice the usable syntax hasn't changed
yet. There's some intent for Unicode module names to be supported in the
future, but this hasn't yet amounted to any consistent facility.
.
The functions of this module whose purpose is to load modules include
workarounds for three old Perl core bugs regarding 'require'. These
workarounds are applied on any Perl version where the bugs exist, except
for a case where one of the bugs cannot be adequately worked around in pure
Perl.
Package: perl-mro-compat
Version: 0.15-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 81
Filename: all/perl-mro-compat_0.15-3.15_all.deb
Size: 17200
MD5sum: 28522c45a1e862284409cf51be5fb69e
SHA1: 2a3fc3a70db18921e6b0498742c5e9659d5b310c
SHA256: a42cac9ee4be0f6614090b6a3c2677b433326dab8d14b8f3c85e928e52b17f70
Priority: optional
Homepage: https://metacpan.org/release/MRO-Compat
Description: Mro::* interface compatibility for Perls < 5.9.5
The "mro" namespace provides several utilities for dealing with method
resolution order and method caching in general in Perl 5.9.5 and higher.
.
This module provides those interfaces for earlier versions of Perl (back to
5.6.0 anyways).
.
It is a harmless no-op to use this module on 5.9.5+. That is to say, code
which properly uses MRO::Compat will work unmodified on both older Perls
and 5.9.5+.
.
If you're writing a piece of software that would like to use the parts of
5.9.5+'s mro:: interfaces that are supported here, and you want
compatibility with older Perls, this is the module for you.
.
Some parts of this code will work better and/or faster with Class::C3::XS
installed (which is an optional prereq of Class::C3, which is in turn a
prereq of this package), but it's not a requirement.
.
This module never exports any functions. All calls must be fully qualified
with the 'mro::' prefix.
.
The interface documentation here serves only as a quick reference of what
the function basically does, and what differences between MRO::Compat and
5.9.5+ one should look out for. The main docs in 5.9.5's mro are the real
interface docs, and contain a lot of other useful information.
Package: perl-parent
Version: 0.241-1.12
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 48
Filename: all/perl-parent_0.241-1.12_all.deb
Size: 8872
MD5sum: e1931031b1283e6aaf1d9e1ba9388597
SHA1: 8d09d517bceb792df3949f61707d64d828cf301f
SHA256: cca3c4c3a00c67bd17d8be68303ab60ff4fa6682b5b5ea4ded5622b71188b959
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/parent
Description: Establish an ISA relationship with base classes at compile time
Allows you to both load one or more modules, while setting up inheritance
from those modules at the same time. Mostly similar in effect to
.
package Baz;
BEGIN {
require Foo;
require Bar;
push @ISA, qw(Foo Bar);
}
.
By default, every base class needs to live in a file of its own. If you
want to have a subclass and its parent class in the same file, you can tell
'parent' not to load any modules by using the '-norequire' switch:
.
package Foo;
sub exclaim { "I CAN HAS PERL" }
.
package DoesNotLoadFooBar;
use parent -norequire, 'Foo', 'Bar';
# will not go looking for Foo.pm or Bar.pm
.
This is equivalent to the following code:
.
package Foo;
sub exclaim { "I CAN HAS PERL" }
.
package DoesNotLoadFooBar;
push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar';
.
This is also helpful for the case where a package lives within a
differently named file:
.
package MyHash;
use Tie::Hash;
use parent -norequire, 'Tie::StdHash';
.
This is equivalent to the following code:
.
package MyHash;
require Tie::Hash;
push @ISA, 'Tie::StdHash';
.
If you want to load a subclass from a file that 'require' would not
consider an eligible filename (that is, it does not end in either '.pm' or
'.pmc'), use the following code:
.
package MySecondPlugin;
require './plugins/custom.plugin'; # contains Plugin::Custom
use parent -norequire, 'Plugin::Custom';
Package: perl-perl-ostype
Version: 1.010-3.20
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-perl-ostype_1.010-3.20_all.deb
Size: 15200
MD5sum: 05e4de2038a7cc9d6090ea2a84528900
SHA1: cac82d08fef94a0d28606d4ba11f45125be379d9
SHA256: 60c072ce54b1d18e5ba52c57b8b15392dadd27eba3deb1dfb67d1bda94b6b34a
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Perl-OSType/
Description: Map Perl operating system names to generic types
Modules that provide OS-specific behaviors often need to know if the
current operating system matches a more generic type of operating systems.
For example, 'linux' is a type of 'Unix' operating system and so is
'freebsd'.
.
This module provides a mapping between an operating system name as given by
'$^O' and a more generic type. The initial version is based on the OS type
mappings provided in Module::Build and ExtUtils::CBuilder. (Thus, Microsoft
operating systems are given the type 'Windows' rather than 'Win32'.)
Package: perl-pod-coverage
Version: 0.23-3.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 85
Depends: perl-devel-symdump,perl
Filename: all/perl-pod-coverage_0.23-3.16_all.deb
Size: 19116
MD5sum: 969594f3d479a3e26349a976218008b3
SHA1: afbc4d4d0ac8aca2adbeea76357883e19d5d24ea
SHA256: cf83c66a2bfb2f41f0c12ab2e6e7f0b96a68e24a295ccde16fbd906910934f22
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/Pod-Coverage
Description: Checks if the documentation of a module is comprehensive
Developers hate writing documentation. They'd hate it even more if their
computer tattled on them, but maybe they'll be even more thankful in the
long run. Even if not, _perlmodstyle_ tells you to, so you must obey.
.
This module provides a mechanism for determining if the pod for a given
module is comprehensive.
.
It expects to find either a '=head(n>1)' or an '=item' block documenting a
subroutine.
.
Consider: # an imaginary Foo.pm package Foo;
.
=item foo
.
The foo sub
.
= cut
.
sub foo {}
sub bar {}
.
1;
__END__
.
In this example 'Foo::foo' is covered, but 'Foo::bar' is not, so the 'Foo'
package is only 50% (0.5) covered
Package: perl-sub-uplevel
Version: 0.2800-2.45
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 112
Filename: all/perl-sub-uplevel_0.2800-2.45_all.deb
Size: 22172
MD5sum: 1c7455f9dd9ad670d88bb46f2b1133ad
SHA1: 01c33761d6a4e4ac16cd23dbfb8ed10d6779ec91
SHA256: 6df1d3fce4b48dcad1b16558b26c91a869c548f4804affc19d75e21a215d26ce
Section: Development/Libraries/Perl
Priority: optional
Homepage: https://metacpan.org/release/Sub-Uplevel
Description: Apparently run a function in a higher stack frame
Like Tcl's uplevel() function, but not quite so dangerous. The idea is
just to fool caller(). All the really naughty bits of Tcl's uplevel()
are avoided.
Package: perl-test-class
Version: 0.52-3.71
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 208
Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny
Filename: all/perl-test-class_0.52-3.71_all.deb
Size: 56796
MD5sum: 7d775d129aaf06e2bc25d7f68b5dd196
SHA1: 7add25bf9da46f036fff3266f43df87b1977594a
SHA256: 187cd45848dcd08c26308d1bfaefdc374d34c684cb3000db98f89d7d0aecca64
Priority: optional
Homepage: https://metacpan.org/release/Test-Class
Description: Easily create test classes in an xUnit/JUnit style
Test::Class provides a simple way of creating classes and objects to test
your code in an xUnit style.
.
Built using Test::Builder, it was designed to work with other Test::Builder
based modules (Test::More, Test::Differences, Test::Exception, etc.).
.
_Note:_ This module will make more sense, if you are already familiar with
the "standard" mechanisms for testing perl code. Those unfamiliar with
Test::Harness, Test::Simple, Test::More and friends should go take a look
at them now. Test::Tutorial is a good starting point.
Package: perl-test-compile
Version: 3.3.1-3.41
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 86
Depends: perl-base,perl-parent
Provides: libtest-compile-perl (= 3.3.1-3.41),libtest-compile-internal-perl (= 3.3.1-3.41)
Filename: all/perl-test-compile_3.3.1-3.41_all.deb
Size: 21448
MD5sum: 244cdeeeb6935b5bea30af9017d4a8e4
SHA1: 7f3358ed7fc1c92f368e7d57e0735eecbe39a39e
SHA256: 532488ea1c8e959ac6315dc2f775f368a47c479daf46f15110c40bc0d931ecfd
Priority: optional
Homepage: https://metacpan.org/release/Test-Compile
Description: Assert that your Perl files compile OK
'Test::Compile' lets you check the whether your perl modules and scripts
compile properly, results are reported in standard 'Test::Simple' fashion.
.
The basic usage - as shown above, will locate your perl files and test that
they all compile.
.
Module authors can (and probably should) include the following in a
_t/00-compile.t_ file and have 'Test::Compile' automatically find and check
all Perl files in a module distribution:
.
#!perl
use strict;
use warnings;
use Test::Compile qw();
.
my $test = Test::Compile->new();
$test->all_files_ok();
$test->done_testing();
Package: perl-test-deep
Version: 1.204-4.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 353
Depends: perl
Filename: all/perl-test-deep_1.204-4.16_all.deb
Size: 92764
MD5sum: 6ca3ad58a993d31bb908d6db0d970ba3
SHA1: c1e0668f98dd7b5bb37afd3c164407026e3ff628
SHA256: 4d2f61d2d03d621f1318da10611217dfe3f9c792d72b41bd954b1bbff0f0ce1c
Priority: optional
Homepage: https://metacpan.org/release/Test-Deep
Description: Extremely flexible deep comparison
If you don't know anything about automated testing in Perl then you should
probably read about Test::Simple and Test::More before preceding.
Test::Deep uses the Test::Builder framework.
.
Test::Deep gives you very flexible ways to check that the result you got is
the result you were expecting. At its simplest it compares two structures
by going through each level, ensuring that the values match, that arrays
and hashes have the same elements and that references are blessed into the
correct class. It also handles circular data structures without getting
caught in an infinite loop.
.
Where it becomes more interesting is in allowing you to do something
besides simple exact comparisons. With strings, the 'eq' operator checks
that 2 strings are exactly equal but sometimes that's not what you want.
When you don't know exactly what the string should be but you do know some
things about how it should look, 'eq' is no good and you must use pattern
matching instead. Test::Deep provides pattern matching for complex data
structures
.
Test::Deep has *_a lot_* of exports. See EXPORTS below.
Package: perl-test-differences
Version: 0.710.0-3.29
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 73
Depends: perl-capture-tiny,perl,perl-text-diff
Provides: libtest-differences-perl (= 0.710.0-3.29)
Filename: all/perl-test-differences_0.710.0-3.29_all.deb
Size: 18376
MD5sum: 0b7b5cf2ef195861560e9d98379bb051
SHA1: 140217b97443a4b5e79268e082d92a4f46fd2dba
SHA256: 9142e347af263ac90a91817bc64ceb2986c49e48f42da5c50d274867c4d97bb4
Priority: optional
Homepage: https://metacpan.org/release/Test-Differences
Description: Test strings and data structures and show differences if not ok
When the code you're testing returns multiple lines, records or data
structures and they're just plain wrong, an equivalent to the Unix 'diff'
utility may be just what's needed. Here's output from an example test
script that checks two text documents and then two (trivial) data
structures:
.
t/99example....1..3
not ok 1 - differences in text
# Failed test ((eval 2) at line 14)
# +---+----------------+----------------+
# | Ln|Got |Expected |
# +---+----------------+----------------+
# | 1|this is line 1 |this is line 1 |
# * 2|this is line 2 |this is line b *
# | 3|this is line 3 |this is line 3 |
# +---+----------------+----------------+
not ok 2 - differences in whitespace
# Failed test ((eval 2) at line 20)
# +---+------------------+------------------+
# | Ln|Got |Expected |
# +---+------------------+------------------+
# | 1| indented | indented |
# * 2| indented |\tindented *
# | 3| indented | indented |
# +---+------------------+------------------+
not ok 3
# Failed test ((eval 2) at line 22)
# +----+-------------------------------------+----------------------------+
# | Elt|Got |Expected |
# +----+-------------------------------------+----------------------------+
# * 0|bless( [ |[ *
# * 1| 'Move along, nothing to see here' | 'Dry, humorless message' *
# * 2|], 'Test::Builder' ) |] *
# +----+-------------------------------------+----------------------------+
# Looks like you failed 3 tests of 3.
.
eq_or_diff_...() compares two strings or (limited) data structures and
either emits an ok indication or a side-by-side diff. Test::Differences is
designed to be used with Test.pm and with Test::Simple, Test::More, and
other Test::Builder based testing modules. As the SYNOPSIS shows, another
testing module must be used as the basis for your test suite.
Package: perl-test-exception
Version: 0.430000-3.48
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 71
Depends: perl-sub-uplevel,perl
Provides: libtest-exception-perl (= 0.430000-3.48)
Filename: all/perl-test-exception_0.430000-3.48_all.deb
Size: 18084
MD5sum: 0f3928ccc48eb7255867a04b33b71594
SHA1: 278a59d7664cfa674c2d100905595113a6394b21
SHA256: 2c32110f32ef177127d73a422ad7627bdbc0663ef8a9f41c64a1fd117d092a45
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Test-Exception/
Description: Test exception-based code
This module provides a few convenience methods for testing exception based
code. It is built with Test::Builder and plays happily with Test::More and
friends.
.
If you are not already familiar with Test::More now would be the time to go
take a look.
.
You can specify the test plan when you 'use Test::Exception' in the same
way as 'use Test::More'. See Test::More for details.
.
NOTE: Test::Exception only checks for exceptions. It will ignore other
methods of stopping program execution - including exit(). If you have an
exit() in evalled code Test::Exception will not catch this with any of its
testing functions.
.
NOTE: This module uses Sub::Uplevel and relies on overriding
'CORE::GLOBAL::caller' to hide your test blocks from the call stack. If
this use of global overrides concerns you, the Test::Fatal module offers a
more minimalist alternative.
.
* *throws_ok*
.
Tests to see that a specific exception is thrown. throws_ok() has two
forms:
.
throws_ok BLOCK REGEX, TEST_DESCRIPTION
throws_ok BLOCK CLASS, TEST_DESCRIPTION
.
In the first form the test passes if the stringified exception matches the
give regular expression. For example:
.
throws_ok { read_file( 'unreadable' ) } qr/No file/, 'no file';
.
If your perl does not support 'qr//' you can also pass a regex-like string,
for example:
.
throws_ok { read_file( 'unreadable' ) } '/No file/', 'no file';
.
The second form of throws_ok() test passes if the exception is of the same
class as the one supplied, or a subclass of that class. For example:
.
throws_ok { $foo->bar } "Error::Simple", 'simple error';
.
Will only pass if the 'bar' method throws an Error::Simple exception, or a
subclass of an Error::Simple exception.
.
You can get the same effect by passing an instance of the exception you
want to look for. The following is equivalent to the previous example:
.
my $SIMPLE = Error::Simple->new;
throws_ok { $foo->bar } $SIMPLE, 'simple error';
.
Should a throws_ok() test fail it produces appropriate diagnostic messages.
For example:
.
not ok 3 - simple error
# Failed test (test.t at line 48)
# expecting: Error::Simple exception
# found: normal exit
.
Like all other Test::Exception functions you can avoid prototypes by
passing a subroutine explicitly:
.
throws_ok( sub {$foo->bar}, "Error::Simple", 'simple error' );
.
A true value is returned if the test succeeds, false otherwise. On exit $@
is guaranteed to be the cause of death (if any).
.
A description of the exception being checked is used if no optional test
description is passed.
.
NOTE: Remember when you 'die $string_without_a_trailing_newline' perl will
automatically add the current script line number, input line number and a
newline. This will form part of the string that throws_ok regular
expressions match against.
.
* *dies_ok*
.
Checks that a piece of code dies, rather than returning normally. For
example:
.
sub div {
my ( $a, $b ) = @_;
return $a / $b;
};
.
dies_ok { div( 1, 0 ) } 'divide by zero detected';
.
# or if you don't like prototypes
dies_ok( sub { div( 1, 0 ) }, 'divide by zero detected' );
.
A true value is returned if the test succeeds, false otherwise. On exit $@
is guaranteed to be the cause of death (if any).
.
Remember: This test will pass if the code dies for any reason. If you care
about the reason it might be more sensible to write a more specific test
using throws_ok().
.
The test description is optional, but recommended.
.
* *lives_ok*
.
Checks that a piece of code doesn't die. This allows your test script to
continue, rather than aborting if you get an unexpected exception. For
example:
.
sub read_file {
my $file = shift;
local $/;
open my $fh, '<', $file or die "open failed ($!)\n";
$file = <FILE>;
return $file;
};
.
my $file;
lives_ok { $file = read_file('test.txt') } 'file read';
.
# or if you don't like prototypes
lives_ok( sub { $file = read_file('test.txt') }, 'file read' );
.
Should a lives_ok() test fail it produces appropriate diagnostic messages.
For example:
.
not ok 1 - file read
# Failed test (test.t at line 15)
# died: open failed (No such file or directory)
.
A true value is returned if the test succeeds, false otherwise. On exit $@
is guaranteed to be the cause of death (if any).
.
The test description is optional, but recommended.
.
* *lives_and*
.
Run a test that may throw an exception. For example, instead of doing:
.
my $file;
lives_ok { $file = read_file('answer.txt') } 'read_file worked';
is $file, "42", 'answer was 42';
.
You can use lives_and() like this:
.
lives_and { is read_file('answer.txt'), "42" } 'answer is 42';
# or if you don't like prototypes
lives_and(sub {is read_file('answer.txt'), "42"}, 'answer is 42');
.
Which is the same as doing
.
is read_file('answer.txt'), "42\n", 'answer is 42';
.
unless 'read_file('answer.txt')' dies, in which case you get the same kind
of error as lives_ok()
.
not ok 1 - answer is 42
# Failed test (test.t at line 15)
# died: open failed (No such file or directory)
.
A true value is returned if the test succeeds, false otherwise. On exit $@
is guaranteed to be the cause of death (if any).
.
The test description is optional, but recommended.
Package: perl-test-most
Version: 0.38-3.71
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
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.38-3.71_all.deb
Size: 23424
MD5sum: 616515708f9fc3f3fdaffeec2f071c4d
SHA1: 2f928b47dde7c40c00cc0bb0b0e3ba8d18414043
SHA256: bfeb03345248efb4f11baff5709a7376dd7051098bc088bbb73c3206d9b4719e
Priority: optional
Homepage: https://metacpan.org/release/Test-Most
Description: Most commonly needed test functions and features
Test::Most exists to reduce boilerplate and to make your testing life
easier. We provide "one stop shopping" for most commonly used testing
modules. In fact, we often require the latest versions so that you get bug
fixes through Test::Most and don't have to keep upgrading these modules
separately.
.
This module provides you with the most commonly used testing functions,
along with automatically turning on strict and warning and gives you a bit
more fine-grained control over your test suite.
.
use Test::Most tests => 4, 'die';
.
ok 1, 'Normal calls to ok() should succeed';
is 2, 2, '... as should all passing tests';
eq_or_diff [3], [4], '... but failing tests should die';
ok 4, '... will never get to here';
.
As you can see, the 'eq_or_diff' test will fail. Because 'die' is in the
import list, the test program will halt at that point.
.
If you do not want strict and warnings enabled, you must explicitly disable
them. Thus, you must be explicit about what you want and no longer need to
worry about accidentally forgetting them.
.
use Test::Most tests => 4;
no strict;
no warnings;
Package: perl-test-pod
Version: 1.52-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 62
Depends: perl
Filename: all/perl-test-pod_1.52-3.15_all.deb
Size: 13316
MD5sum: feefa679821be632fd666bdf8004a036
SHA1: 07865f4018a7706d7a0e93f1619ca096a630e89d
SHA256: 7751632f9ae6edec144c1a4ace91b4d1483777da368cabdaa8ef513e3ce00846
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Test-Pod/
Description: Check for Pod Errors in Files
Check POD files for errors or warnings in a test file, using 'Pod::Simple'
to do the heavy lifting.
Package: perl-test-pod-coverage
Version: 1.10-3.18
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 61
Depends: perl-pod-coverage
Filename: all/perl-test-pod-coverage_1.10-3.18_all.deb
Size: 10928
MD5sum: b88c9634664a2410a4325ba583e8f88b
SHA1: 817c01c09bfc2bc2e3cf409c1d860ad9c96a082d
SHA256: f74c109fc01465f3269acc3213552b94dc847cc9be51f623a9466cc0d210797c
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Test-Pod-Coverage/
Description: Check for pod coverage in your distribution.
Test::Pod::Coverage is used to create a test for your distribution, to
ensure that all relevant files in your distribution are appropriately
documented in pod.
.
Can also be called with the Pod::Coverage manpage parms.
.
use Test::Pod::Coverage tests=>1;
pod_coverage_ok(
"Foo::Bar",
{ also_private => [ qr/^[A-Z_]+$/ ], },
"Foo::Bar, with all-caps functions as privates",
);
.
The the Pod::Coverage manpage parms are also useful for subclasses that
don't re-document the parent class's methods. Here's an example from the
Mail::SRS manpage.
.
pod_coverage_ok( "Mail::SRS" ); # No exceptions
.
# Define the three overridden methods.
my $trustme = { trustme => [qr/^(new|parse|compile)$/] };
pod_coverage_ok( "Mail::SRS::DB", $trustme );
pod_coverage_ok( "Mail::SRS::Guarded", $trustme );
pod_coverage_ok( "Mail::SRS::Reversable", $trustme );
pod_coverage_ok( "Mail::SRS::Shortcut", $trustme );
.
Alternately, you could use the Pod::Coverage::CountParents manpage, which
always allows a subclass to reimplement its parents' methods without
redocumenting them. For example:
.
my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' };
pod_coverage_ok( "IO::Handle::Frayed", $trustparents );
.
(The 'coverage_class' parameter is not passed to the coverage class with
other parameters.)
.
If you want POD coverage for your module, but don't want to make
Test::Pod::Coverage a prerequisite for installing, create the following as
your _t/pod-coverage.t_ file:
.
use Test::More;
eval "use Test::Pod::Coverage";
plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@;
.
plan tests => 1;
pod_coverage_ok( "Pod::Master::Html");
.
Finally, Module authors can include the following in a _t/pod-coverage.t_
file and have 'Test::Pod::Coverage' automatically find and check all
modules in the module distribution:
.
use Test::More;
eval "use Test::Pod::Coverage 1.00";
plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@;
all_pod_coverage_ok();
Package: perl-test-warn
Version: 0.37-3.47
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 70
Depends: perl-carp,perl-sub-uplevel
Filename: all/perl-test-warn_0.37-3.47_all.deb
Size: 14840
MD5sum: f975b542eb58876f2a2c1ef66f8723ba
SHA1: 605238782925af0eb8cc2497ed72131e8c5beec0
SHA256: b0d180a8d76640a2c81cfc5d8929fc9e67deb93d3953ca22a6018015ba29980a
Priority: optional
Homepage: https://metacpan.org/release/Test-Warn
Description: Perl extension to test methods for warnings
A good style of Perl programming calls for a lot of diverse regression
tests.
.
This module provides a few convenience methods for testing warning
based-code.
.
If you are not already familiar with the Test::More manpage now would be
the time to go take a look.
Package: perl-text-diff
Version: 1.45-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 129
Depends: libalgorithm-diff-perl
Filename: all/perl-text-diff_1.45-3.15_all.deb
Size: 33332
MD5sum: 4eb0ffc9ffe667e02d0bebf62c1e34bc
SHA1: d0bf6cead2bc9045010ffd1c1e5f544ef93a1f8b
SHA256: 065b4620f58979c5dcb86544ce97fa4f371adf67b04b9efd3572febe8bed0fec
Section: Development/Libraries/Perl
Priority: optional
Homepage: http://search.cpan.org/dist/Text-Diff/
Description: Perform diffs on files and record sets
'diff()' provides a basic set of services akin to the GNU 'diff' utility.
It is not anywhere near as feature complete as GNU 'diff', but it is better
integrated with Perl and available on all platforms. It is often faster
than shelling out to a system's 'diff' executable for small files, and
generally slower on larger files.
.
Relies on Algorithm::Diff for, well, the algorithm. This may not produce
the same exact diff as a system's local 'diff' executable, but it will be a
valid diff and comprehensible by 'patch'. We haven't seen any differences
between Algorithm::Diff's logic and GNU 'diff''s, but we have not examined
them to make sure they are indeed identical.
.
*Note*: If you don't want to import the 'diff' function, do one of the
following:
.
use Text::Diff ();
.
require Text::Diff;
.
That's a pretty rare occurrence, so 'diff()' is exported by default.
.
If you pass a filename, but the file can't be read, then 'diff()' will
'croak'.
Package: perl-try-tiny
Version: 0.31-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 80
Filename: all/perl-try-tiny_0.31-3.15_all.deb
Size: 23980
MD5sum: d4cc63cd89a1b2a1fe06e987517df08f
SHA1: 7ad6b53163bed91fc5e58c4d496ce06458b1c561
SHA256: c40c2c4cd492509a55c041a4be6b4b86e978c86039a214fc9de8a7eab8d264a5
Priority: optional
Homepage: https://metacpan.org/release/Try-Tiny
Description: Minimal try/catch with proper preservation of $@
This module provides bare bones 'try'/'catch'/'finally' statements that are
designed to minimize common mistakes with eval blocks, and NOTHING else.
.
This is unlike TryCatch which provides a nice syntax and avoids adding
another call stack layer, and supports calling 'return' from the 'try'
block to return from the parent subroutine. These extra features come at a
cost of a few dependencies, namely Devel::Declare and Scope::Upper which
are occasionally problematic, and the additional catch filtering uses Moose
type constraints which may not be desirable either.
.
The main focus of this module is to provide simple and reliable error
handling for those having a hard time installing TryCatch, but who still
want to write correct 'eval' blocks without 5 lines of boilerplate each
time.
.
It's designed to work as correctly as possible in light of the various
pathological edge cases (see BACKGROUND) and to be compatible with any
style of error values (simple strings, references, objects, overloaded
objects, etc).
.
If the 'try' block dies, it returns the value of the last statement
executed in the 'catch' block, if there is one. Otherwise, it returns
'undef' in scalar context or the empty list in list context. The following
examples all assign '"bar"' to '$x':
.
my $x = try { die "foo" } catch { "bar" };
my $x = try { die "foo" } || "bar";
my $x = (try { die "foo" }) // "bar";
.
my $x = eval { die "foo" } || "bar";
.
You can add 'finally' blocks, yielding the following:
.
my $x;
try { die 'foo' } finally { $x = 'bar' };
try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' };
.
'finally' blocks are always executed making them suitable for cleanup code
which cannot be handled using local. You can add as many 'finally' blocks
to a given 'try' block as you like.
.
Note that adding a 'finally' block without a preceding 'catch' block
suppresses any errors. This behaviour is consistent with using a standalone
'eval', but it is not consistent with 'try'/'finally' patterns found in
other programming languages, such as Java, Python, Javascript or C#. If you
learned the 'try'/'finally' pattern from one of these languages, watch out
for this.
Package: perl-universal-require
Version: 0.19-3.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 52
Filename: all/perl-universal-require_0.19-3.15_all.deb
Size: 8924
MD5sum: 244796fb4c36b54ff95e4612d9e9bbcf
SHA1: 83b7381d804717ec521c0ae14686601d9ffc04f0
SHA256: 7175d3ba9eddfd49ff677e73da5c244d3fed841729fa271681804bdebd57086b
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.