Package: deb-perl-macros
Version: 0.1-26.5
Architecture: all
Maintainer: Victor Zhestkov <vzhestkov@suse.com>
Installed-Size: 42
Depends: perl
Filename: all/deb-perl-macros_0.1-26.5_all.deb
Size: 2704
MD5sum: d18e470ca98db8189cebb56592b4e67d
SHA1: 1e94cdc880662df69d00e20cc6a094ff9971e964
SHA256: a0326d0eb30a7fab169e4e399880a7f9644b74e5cf6a7dd479f2ccd2da202494
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.1
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-39.1_all.deb
Size: 55136
MD5sum: 617f35338fb2d643ff5cb4e61e980a4c
SHA1: 057efb0c1a58d10864e86843baf2fa44570dcb43
SHA256: 8675c3384935abfb6338882d723b93ca4db4b1f5052c7652283a8fc62885df55
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.1
Architecture: all
Maintainer: debbuild developers <https://github.com/debbuild/debbuild>
Installed-Size: 32
Depends: debbuild (= 24.12.0-39.1),liblua-api-perl
Filename: all/debbuild-lua-support_24.12.0-39.1_all.deb
Size: 8624
MD5sum: c47bc4fee53fedeee04b644b5d9859de
SHA1: eee41739711ed21ad1f57999672618011c600558
SHA256: 3d6690ca87766c178ef5850fe1e2e189ebe47c3e2c6c2d9a32248dda1c616e0e
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-17.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-17.1_all.deb
Size: 25488
MD5sum: d01b9e43475bbc04c3123eec1b682a42
SHA1: 9e43a46daa76f00f1709c24f799203910f97c163
SHA256: ee63fd48151d60a2d7364dc7ed9d1f29a69be66e6bb83162237359cca5c7d115
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-57.1
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 856
Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-57.1)
Provides: lua51-libs (= 5.1.5-57.1),liblua5-1 (= 5.1.5-57.1)
Filename: amd64/liblua5-1-5_5.1.5-57.1_amd64.deb
Size: 243988
MD5sum: 363a9bf5b53a708de308f35542ba5bf3
SHA1: 18c13b18f5a97bb4cd3b40335964ea337fb98584
SHA256: 8c292cc5f3c60a2a4f07deb4dffbab061d4d17bb647501526570fb535fb05ba5
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-48.1
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 25
Filename: all/lua-macros_20210827-48.1_all.deb
Size: 1520
MD5sum: b70300c0f53f4063fe2d2f5a576a33d7
SHA1: 87193f09e1a9c1448c653b4cb4e28ae44962079c
SHA256: 191af6e2e48b834426626a55f02c41f79ed6c8d0c587b0a9760a6e9e7f99838c
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-57.1
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1482
Depends: dpkg,libreadline7,libc6,libtinfo5
Provides: lua (= 5.1.5-57.1),lua-api (= 5.1)
Filename: amd64/lua51_5.1.5-57.1_amd64.deb
Size: 297192
MD5sum: 195de6cb31b860c1fd7d483cb47b5aa1
SHA1: 871c4bc0a5d05003873e232f84663697f454ab84
SHA256: 5aebe3d09e5e14d5b45480efd651b3bd41e5a4f28ce7e910f08d86d3322bdfbc
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-57.1
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 1529
Depends: liblua5-1-5 (= 5.1.5-57.1),lua51 (= 5.1.5-57.1),lua-macros,dpkg
Provides: lua-devel (= 5.1.5-57.1),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-57.1)
Filename: amd64/lua51-devel_5.1.5-57.1_amd64.deb
Size: 313932
MD5sum: 966354004d859d5e727c32bff4f065ba
SHA1: 78778cc452d8aeec538208b834a1b8655c34ad52
SHA256: 32c6ef14236115afe628664c5390634ee612d97bb97d07c4862ed15abb8feba1
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-57.1
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 330
Filename: all/lua51-doc_5.1.5-57.1_all.deb
Size: 71628
MD5sum: 98662397f248d2a8e9fc0f6caccadbe5
SHA1: 97a1eaeeff9cb3dfbaa8149df1ed4ad4eb8bb1fc
SHA256: ba1703b9397bc25994a13fcf58a299a5a2dfddf4cf1a36c202faa3a794b9136f
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 121
Filename: all/perl-capture-tiny_0.48-26.4_all.deb
Size: 29960
MD5sum: 53e5eb471c301cab1c4f6b647fc04243
SHA1: e54e1f28e8317c5c008fb1a15cc65807687fe26a
SHA256: 807b9f17b984aedf998f814b23b927c2de337dbbe0c74841f6b5e66a95b3676a
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 88
Filename: all/perl-carp_1.50-26.4_all.deb
Size: 22660
MD5sum: d73746e902a3e32d33f885ea373e6e41
SHA1: 1c5ea73b40f3ddaecfe9702497153102ea5d34bd
SHA256: 612a280f0e1ac0c29cadb0effe3fe7bd35fdee5514e888f735ce76ea7c618f65
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 55
Filename: all/perl-class-data-inheritable_0.09-26.4_all.deb
Size: 7204
MD5sum: bffa92a9a87f49bdc2d559c029b2efc3
SHA1: 9dfa2940c87a1091398fb5b8e3d34efbdf61529c
SHA256: 35fd17d25535550ee20f0b8525500936f2016c429c846efecb42525568a7cb2c
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 113
Filename: all/perl-devel-stacktrace_2.04-26.4_all.deb
Size: 28348
MD5sum: 267afe141195774c3ea1f737b1aa884d
SHA1: 3680f34a0a757a96c1810139fe1a298130e22a32
SHA256: e8d6ae70cc36febf7654c341333c643440ab1e3bfdbeffcfc0dd0d9686416f75
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 76
Depends: perl
Filename: all/perl-devel-symdump_2.18-26.4_all.deb
Size: 14340
MD5sum: cfd610b8280b30c59509645eb85b7f53
SHA1: 47948f813b012ef441c3b54a8db773f8c755595b
SHA256: 7cd4a7e75feb0c36cae18cbb92bd828f62fbf453c7b14f445193fa9c99ae7b13
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-26.8
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-26.8_all.deb
Size: 38968
MD5sum: 0b7165481a99c214497446d9c120250e
SHA1: 7270de84af730ebee639b6367c2db1791786116e
SHA256: f45c19f99d9b36c0c4763920401ce37f0228e7a4d3273ed0174c251bf74eb300
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-25.11
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-25.11_all.deb
Size: 39208
MD5sum: fa8f7b5aae63411bd51cc28fda9638a9
SHA1: 3100d602d64e94c9a95439bb871d4f46a6cb2dbc
SHA256: 0f85e7bd63d43b8cf60f2671bb62f9b70c8ef93234a5f6e17dff1a7d2235d2dd
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-11.5
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 889
Filename: all/perl-extutils-makemaker_7.66-11.5_all.deb
Size: 303140
MD5sum: a7d02ef6b1dbf8223cd78d5d23b6c5e4
SHA1: ec752c0f135335a568620ff3c1a033ff794cce4c
SHA256: 79a914db383b309e07de3cd10fbad8c670c1616a0fd36cca427a5e31105c7eb6
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 61
Depends: pkg-config
Provides: libextutils-pkgconfig-perl (= 1.160000-26.4)
Filename: all/perl-extutils-pkgconfig_1.160000-26.4_all.deb
Size: 10536
MD5sum: eb0b640e218d17966dc9873e9aa14a16
SHA1: 34a582232d106d4efb511835ad34a98a4886b801
SHA256: 9f361de865392a00324604f8e2c0b44b5a12931274da22710a8dff8009e9f873
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 107
Provides: libfile-path-perl (= 2.180000-26.4)
Filename: all/perl-file-path_2.180000-26.4_all.deb
Size: 30636
MD5sum: da8c3ca6815977c462b06de8a2dfb7dd
SHA1: b6054a33a25c6b5b855f08689ee39761cdb658d2
SHA256: 1d65abd2f2a1ed688401bfeb6e8f10f0211757c683ea7636e81d60537ff0e4a3
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-26.6
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-26.6_all.deb
Size: 53276
MD5sum: 180d6485ac4b0b42663fc6ef818d55fe
SHA1: 5d191f9c259953ad376293746b7db91c47428234
SHA256: 577806c3e8bc4e10edc897c86f17bd4159efa1829b3b255eb9f052686bb5e79a
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 127
Depends: perl
Filename: all/perl-ipc-cmd_1.04-26.4_all.deb
Size: 33120
MD5sum: d26541218e46be6f7975a6d01da783d4
SHA1: 69ab77eb0b4aedae4a971910dd439bdaf8f4cec0
SHA256: f6a5148952a9a60f5ac7bf048bbf81fc1246efea39a81dd24d3ec89921750ae5
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-27.38
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 793
Depends: perl-base,liblua5-1-5,libc6
Filename: amd64/perl-lua-api_0.04-27.38_amd64.deb
Size: 174208
MD5sum: 69270bfa98cfa18034a98187ce766e66
SHA1: b54623b589b6886ee61f3d675d90a56e53a7faef
SHA256: dcdc4364baae6a986f684594b8f4e42866f1e79dab9acb61f463f37e51368874
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-29.10
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 732
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-29.10)
Filename: all/perl-module-build_0.423400-29.10_all.deb
Size: 250876
MD5sum: c4f7b52aa1868168acfde5a9168ee8f4
SHA1: 346789197abb0d0d9a3dd43213734856f9eb8673
SHA256: 16c354b609b8e507be52f8a3e38364164a6735a39134b1c5690f6c92a312892a
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 111
Depends: perl
Filename: all/perl-module-metadata_1.000038-26.4_all.deb
Size: 29612
MD5sum: 5ab7b307058137a7e2225a21419c7683
SHA1: cda7e56b33a50e873be9546059ef4bd962bbb08e
SHA256: b13b05e4c358a3936a06ddc14cb23fbf0b2dac8ff5ba017393f12574090ff146
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-26.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-module-runtime_0.016-26.16_all.deb
Size: 18412
MD5sum: 3ac155282df34372726d88c479f82aef
SHA1: bb12a08c8e9d2eee5e4864771db498eba6397baf
SHA256: be7e3ac3c275ed3dbce31cfd9f011e1479b878c175fbcbbc9c9356310b59ea99
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 81
Filename: all/perl-mro-compat_0.15-26.4_all.deb
Size: 17176
MD5sum: d17c981adeaf971d88a335f7ede36975
SHA1: 985e2ff2506bf2dc6aa4262e1cb8130ce86429c5
SHA256: 6f5fbc4039b350c85d29cce4c4264b9aa8e8fe54f7cb8a712d79c7f42e83f21b
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.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 48
Filename: all/perl-parent_0.241-1.4_all.deb
Size: 8848
MD5sum: 60c5237856f2622b7bc50339c2c0e5b9
SHA1: 8995bcb65dc98bbcf12e46d71a5a5f8783cd2a5b
SHA256: 2e6350489630f920b423fa88db0e5a55a3f52ca79ceb01ec3bf8e3983767ff29
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-26.5
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-perl-ostype_1.010-26.5_all.deb
Size: 15164
MD5sum: 32a1a5ab575604e02da39a11dfeaa928
SHA1: 6f705715eefc8d7f6c8e1c60f47c7c0250207a31
SHA256: aef414bf483f8f8169d24c96fa996df1936ae74575d274b1709b5e6c6ebb7572
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-28.6
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-28.6_all.deb
Size: 19028
MD5sum: 108f89c7c57d17529e8bfc94cce847ba
SHA1: ab7cfeff17c3ffda420f518ea35a5d35b521186d
SHA256: c0c4495495c5c8fc0c52aee650d615c90c6d046dfb095030935f823cd3fcfaf2
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-25.17
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 112
Filename: all/perl-sub-uplevel_0.2800-25.17_all.deb
Size: 22140
MD5sum: aca3fb81dd51b94158bb00782b7020fe
SHA1: 4445d7d9c0533ee4a5a189063edd9856c218cc5f
SHA256: edf4a299d9fa909d1fbb842f5bd92904f775129ed2076c752a0109647435ab6e
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-26.25
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 207
Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny
Filename: all/perl-test-class_0.52-26.25_all.deb
Size: 56692
MD5sum: 5cfac61618e91f7c8e0800bed0cd30db
SHA1: 25de707296ad253e20cbf856324e0da4f6307bd1
SHA256: c1070c4847f43cad7876909c8396147e780b3d8f528453185d9ab9aa380d9ea1
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-26.15
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-26.15),libtest-compile-internal-perl (= 3.3.1-26.15)
Filename: all/perl-test-compile_3.3.1-26.15_all.deb
Size: 21400
MD5sum: d9d69a36f4467dcd88396d5bfc041192
SHA1: 8c019e2d5c833820e7290c329b910971885628b6
SHA256: 8dda1f637be7225eb9a0cdb2315c1f128c3ec924c201d3431ca70564670face5
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-27.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 352
Depends: perl
Filename: all/perl-test-deep_1.204-27.4_all.deb
Size: 81652
MD5sum: 82d39b4363dd0e7402e6e1dfef80487b
SHA1: 90989c8861ed06a21ae104b6a6667244f629e7bf
SHA256: 98869a27c49e4182cfab83749ed441984a973c49e221dbf2d099c61dae9324d7
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-26.8
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-26.8)
Filename: all/perl-test-differences_0.710.0-26.8_all.deb
Size: 18344
MD5sum: 0cc94f39ae1e928e66d669248a746825
SHA1: ea190579cd11d97a3bc89057ac214101502d6077
SHA256: e5697d8de6c2a2f9314525559e5109b1228785915575da6be72297250b481d38
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-26.16
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 71
Depends: perl-sub-uplevel,perl
Provides: libtest-exception-perl (= 0.430000-26.16)
Filename: all/perl-test-exception_0.430000-26.16_all.deb
Size: 18060
MD5sum: d96573ee31e522441e2189095de60742
SHA1: 318e21c97b3c21930415d8b6e459c4abe65394ff
SHA256: d82dcc0697e2a8977a5e531a6b26a8f28ff757533801292a7f41934ea86faef8
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-26.25
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-26.25_all.deb
Size: 23384
MD5sum: 6672eff7aca90e9f215172fbb9301163
SHA1: 886e48cad5d91d6b86b4e675ab8dd224e667e215
SHA256: 8a669b898cb7feb947ef713742ec3461ff3978c75c7da970403245d02ffef982
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 62
Depends: perl
Filename: all/perl-test-pod_1.52-26.4_all.deb
Size: 13288
MD5sum: d994f226ab0bc06fd2fa3e7fc4a66842
SHA1: b817f6574b24f618a81e0f505c3e0e93b18fe80d
SHA256: 4615aa050ee74466d72b363f97154b96cc8d3335a59fa5f7222c2bf98738d9dc
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-27.7
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-27.7_all.deb
Size: 10900
MD5sum: bb262de7e799bdc6433acb694d5ad458
SHA1: 4ac8c17ca7785faad29a95d06c495e214683596d
SHA256: db22918b956abec32d6093e87626e3e131b0ceb583a1c989c06754102c06a6e1
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-26.17
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-26.17_all.deb
Size: 14816
MD5sum: 2b623258661bf3a23de8d17f4957abed
SHA1: 2d847a61a725cd73c5584d4022c67f2efbf931b3
SHA256: 871e57eb3fb83bac06c1252e9aa1d1e8e6f0776b8e0ed93e968cb512aca6676c
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 129
Depends: libalgorithm-diff-perl
Filename: all/perl-text-diff_1.45-26.4_all.deb
Size: 33248
MD5sum: 7e6c7e681cb2e9a3f0fca31cfb439d18
SHA1: b7b46ba540406cfc1a194d12d803050fe4d4695f
SHA256: cfbf7c8249343ce6a9243c815d25989709aaac4c5985d0c366e084690109653f
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 80
Filename: all/perl-try-tiny_0.31-26.4_all.deb
Size: 23948
MD5sum: 366efdda5555fea84b89c6c58626d882
SHA1: 949b357c88798032a5ec8d095bb2540d59a33f63
SHA256: 2ad6b13c233c5ccedf22e8fd430fb64d1d99c1d7547471a494885cd2279087c1
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-26.4
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 52
Filename: all/perl-universal-require_0.19-26.4_all.deb
Size: 8884
MD5sum: cc0021af20e9934b5f02524df66e5759
SHA1: 5c9c6f7ed1a2918cc0aecc9c88bd2aa2834370ce
SHA256: 7b495eb36222ca2747b83f82b368402490aed2c4faf4f47cf6c8963e7dd842a2
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.