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: fe4592dad4921bd66a25be5923915889
SHA1: d0104a6df63e0e36ca1812ea18b351fb3709309a
SHA256: 720f4d53c87b4ff03a8b913da5044c544281fd8ae9499bb534993b6ff0e481b0
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: 55164
MD5sum: cc52ec66ab6da53aea341ad53a5cb4a9
SHA1: db66d0ca1c6e0c38f736b08ad71e22aed2e43fe5
SHA256: 9e253dcde1cd83f874e51ab81550f7508fbad33cd63fac9368974ef44a13050e
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: ce605d0698409868dc8c3ee2e78d8dbe
SHA1: d0e450128f1e6e4c6a4df9482d67edb0196d4532
SHA256: 2bf58eea84d49079ac58d0daf4c8c871efb692198a2c155b25ea63ba383ed7cb
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: 25500
MD5sum: c251e56363c83e9a0aad1da10e0522bb
SHA1: d2a9eee345983b38321dc151a1ed19ec88827f47
SHA256: d0268bcc273448ee1acbb874321efca05bc90f5a2696c7435269c187543df962
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: 986
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: 284504
MD5sum: 163d1ff81c3df9b0304bde5e886c9ee0
SHA1: ef3b56f264a1b5064d9a64734255924f9c14e72a
SHA256: 379f3ce488a1b85cfa793b4903594e5a1d39f9bf7276e74d9ebd52d085a3cd1a
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: 1524
MD5sum: 237c17701bc4046a490d5bcad70beb14
SHA1: 57d044bc911f361c0bee49f3b7a29327a658a913
SHA256: 6f4972ef5ca9cae8adfa53354ded6a1b0c6127f452f767fa242affe2bf82d94b
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: 1705
Depends: dpkg,libc6,libreadline8,libtinfo6
Provides: lua (= 5.1.5-57.1),lua-api (= 5.1)
Filename: amd64/lua51_5.1.5-57.1_amd64.deb
Size: 356416
MD5sum: e7e2464ae085414811fb99e362a08b09
SHA1: e66f53f385f33785bfb7eef7bd37a1f431dfe271
SHA256: b7cfd192259aa51b639e453c4e9f796ef81837c183d9d387fe2322370acf3ea0
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: 1884
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: 363804
MD5sum: a1bca7cb843055e85094921457b9dfbf
SHA1: f27953a6a013ab7ad079bb38733783a8213b1dd6
SHA256: 15afa023d4ba624f3ee540d83102ac9b67815a65ccb6bf6084f69c064e1d523d
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: 71700
MD5sum: 38f811cdafa297a62207d245f1463e9e
SHA1: 112617691c03b961ad02cf82c817b8bc45d4c6e8
SHA256: c01654826b9e6df605aa4738a16fe2f7ab98606325007bede7c585ffd23f1f9e
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: 30016
MD5sum: 06e807fb3b769f6710acd9bf6ded5e37
SHA1: 9d1f094c6724baf85330993449617107e20abee3
SHA256: e822d5072d1c5692c108931e6a86edbda16d5ed394a086b95b69850f4e27026a
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: 22676
MD5sum: e0ea31f2211bd38df338be7211cbeb25
SHA1: 13df435122a37d0351d02ae07755d6bd17bde56e
SHA256: 40a58f242942701b9c912a13bc4164df002b1c7c7ff3e1c7488f3da6d86df1d5
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: 7236
MD5sum: 4dbdecec3ca65406b1d378a021e76be2
SHA1: 37e269969c7ac1cec533901e1b1474abc75bf5ea
SHA256: 9b04aa46deb273a2e388d3e0b0b99c14e5a2feaf64ea5f252d865ef22c5600b8
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: 28420
MD5sum: bcef0c67fce12179b2e9c8a4e46f09f2
SHA1: 001bf04b2d5b5a51431736a65df3479bad60e109
SHA256: 30532bac16841e4c67d591dc9dd57b266239c09ea4af31858a1d0ca85ce787e1
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: 14368
MD5sum: d6402a432996bfcb20a601c4b16e0369
SHA1: 50b54a4184d078d0d4c0ffb5e60a6fc4aecc8f58
SHA256: e73be40f0c2d605a11a940c89b7536c4373feac533ae0acb629b487c5fe8277b
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.7
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.7_all.deb
Size: 39044
MD5sum: 4891258ff8803f46f47a22f9214c9f59
SHA1: acaf7852054b5df69c9859db7176df89f131c667
SHA256: 73b156d9af1a37dc554dcf9798aa573af81f28a6bac5cc4909085601acea4224
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: 39260
MD5sum: ab0233a2ea488ca296b0b0847b1a112f
SHA1: 371050d68f49cb99a8116744919c38b6fdfa891e
SHA256: 2d5e1e686f52873528a5d6a2a65d04bbb5f9ccecc0ff6b2585c1be3bed26be71
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: 890
Filename: all/perl-extutils-makemaker_7.66-11.5_all.deb
Size: 304420
MD5sum: ea909e5f08deb1104b49c1134e1b83b1
SHA1: ee713f62b350b8155b188ce9d49c8e3b3c12c250
SHA256: 31d0e84e836e13f1a86a46ef0b0885ed694fce7b49f55babba3433c21add2baa
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: 10556
MD5sum: 03871efe2b2cfe55588358e4ab4c6f93
SHA1: 7187f3b815086162d77c0ded7f135fcf35399d8c
SHA256: 6da71e8af3d1354f4398439c287fd7b04cdcb42e33c6536c1e33d8ccb601353a
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: 30672
MD5sum: 8b4541d2438e502646c646c69638d947
SHA1: 0f7ea8984c669ba0921d636613818a47d7aa19e8
SHA256: 1cde65826899414271f04c90a3408e591e660f83bae46bae94fca81bea0c3b30
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: 53292
MD5sum: 8b4ceb166b09ee221b174b316d072049
SHA1: fba12c14dadb5a3f9f9390787ec76f9e85828fcf
SHA256: 87e02ef45d7f1cbdbf049639746d3e1cf2ee33ba688e331f15e06573178beb22
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: 33148
MD5sum: e23cf0ac8f4e1c0d23d1ae951ae62795
SHA1: b8f212d44dbf44f08e8f0636a4448b36fffe5a96
SHA256: 446c4bfc8fadd40ebc2a09a7ddca8f6fef653765281e913cfd938c3b671cc980
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.34
Architecture: amd64
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 881
Depends: perl-base,liblua5-1-5,libc6
Filename: amd64/perl-lua-api_0.04-27.34_amd64.deb
Size: 186288
MD5sum: 2ded6ed760f2fca47654edfc84d9b097
SHA1: 95afa4c2fa40f6336e59d851eb55ff91e76c3154
SHA256: b0962c9ff4cf48a00242e3f1db523a5cdf66a745b016849b54b8ce253c7e879d
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: 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-29.10)
Filename: all/perl-module-build_0.423400-29.10_all.deb
Size: 251812
MD5sum: 83cb60984a6fab2ce3a500bfb40c11ff
SHA1: bbd452f139c9ba93f856f4918e0ff0327ba82194
SHA256: cf3d0ed4120f111cb7b3cf52c164cd58c48b3368a5cfefe4e64875746b56fcc3
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: 29656
MD5sum: 54b2d970851e1a173f5156812ac25f56
SHA1: 169afb695a26757c677e616df5dd21ba37db8c13
SHA256: c28cc91fbbb9cbe7730e51118e6fa3e8cebaacb2f76a9f9aa877211e074d3eaa
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.15
Architecture: all
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 74
Filename: all/perl-module-runtime_0.016-26.15_all.deb
Size: 18452
MD5sum: d411363c560f3bbc08a34a10d8675097
SHA1: 2f15d39147ec31ff7c0f80edc9652813d89ee3f7
SHA256: 2d2bc88c3fe33d9559fd9718a11b1bdb9fc8a56b034d6c87e558d093b8955a00
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: 17212
MD5sum: 0ae6a103469ddc9c31175a049709d4c4
SHA1: ba9cbfdeaf3138e1aac1e348bd1d41cdd5ecff2c
SHA256: 548665a4a1ddb3b7c7a0eb696f1f1df74a1bede11eccf8e5ee8ffa6c8aa05e63
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: 8872
MD5sum: 825d817529d62acd8ebf8142cc05963a
SHA1: 0ed3e3b7c2f1a2a45c45d331fa3d7ffbf4b7ae23
SHA256: 6236db76b9c7f5764b2491041f61d7f9a1e7e26b6fface1017a0d0e8c981d3e5
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: 15196
MD5sum: d9c08869fa0aa3e27470ef3d59004bb1
SHA1: 7d51b005ab88e38e2782f1b5a1eae042ff18b09d
SHA256: ab36c8e609063eb203f54f8ec8262079d88be4d09d33bf05c5ecddb7671ba1cd
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: 19120
MD5sum: 5b244a817451dec93df25c76e5623d28
SHA1: 49a3af59b9f15e3c15ec681f5f78e7dc9b148324
SHA256: b58cadf331133e4296a0646f78a455edbbc30beda5e9d4c0f3665de36bd0bef9
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: 22184
MD5sum: 741548a4a403eeb71961438123f3a4d1
SHA1: dcddaa2886af4269cb86b2732ad7a43d5ec2c9cc
SHA256: 41d3657337d8bfbe7e0c2a9a104e64501a990765e9214c7389aac2d1136b3656
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.23
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-26.23_all.deb
Size: 56812
MD5sum: 7c4bc83fbb70be255ed5edaac653d39c
SHA1: ef20a817522e9e0fcffa4b38f313f012f870530c
SHA256: 068cb445c5e0e686693985cfb718d2d22c36cedb67117c2f993259e00cf813ed
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.14
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.14),libtest-compile-internal-perl (= 3.3.1-26.14)
Filename: all/perl-test-compile_3.3.1-26.14_all.deb
Size: 21444
MD5sum: 464a488681f33b09e922d618882ab15e
SHA1: 6da0c4c43a5770b28a79c57a5200e6c0c73de71d
SHA256: ab77956d53837e5f0f3ff71309de4fb34afaad8642e4bf4590fa03e19048aacd
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: 353
Depends: perl
Filename: all/perl-test-deep_1.204-27.4_all.deb
Size: 91872
MD5sum: 8bebcb7fc69c64740ecafa4d00d6d355
SHA1: 1331064f4a42b0da2a2c788ee313ca3c9f17e4f7
SHA256: a91844101e640e13b61a2c5143ffebaa4adb55841716e7a7547c162e65d271f8
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: 18388
MD5sum: 9cac1cbbcd3b89b939a13c66f93a1796
SHA1: 8ec7b641b06d2068d28f4875bae66bca00f13d99
SHA256: 437cd537e0c843d128dc2d8803618dcf2c193097befe717f6268d62bcef815b5
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.15
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.15)
Filename: all/perl-test-exception_0.430000-26.15_all.deb
Size: 18092
MD5sum: a9df266655ec0977ca36bf3bbad25e53
SHA1: 052cd11a510be9fabfd3296d94818b73359031e6
SHA256: 74c60a64c9fc5f97efd483b9c649babe785e9f3f60ca801eba6e9fa6f032ee52
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.22
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.22_all.deb
Size: 23436
MD5sum: 75a2c6c0aa4be4206fc27dd13848ae73
SHA1: b5f4120c473ea3cc972db67328d5ec43e438fe3a
SHA256: d047b7cd7bd8b05a53a27d0ed7adf862496a62c097ee4b5f3ef6298c66348185
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: 13324
MD5sum: 00462f4b2bc5f96c0c72c7ad37315fbd
SHA1: cacf0d7988f3a84cf64b157a07db6bc33ef34371
SHA256: 5faa89eb9d1ccdbe31a2e6ec5993853ae510f3e491ebb9dbb99081f95aa93099
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.9
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.9_all.deb
Size: 10936
MD5sum: 8b6c3eaf08944c5b70099dd9a3be054a
SHA1: a8d879261a8a697a15123af8c7e231f4e24838a1
SHA256: 353745e76694fbed1e268f1c3ef4c972e1aa48700d2de11019e0e02e5d6d8422
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.15
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.15_all.deb
Size: 14848
MD5sum: 9435c940b5bf25ba97d9c4f6f6fc578e
SHA1: eed20faab05337a4e28486c5124878d690f82d39
SHA256: f82028986fab09419afe77f8fc395f3a6870b546ffcf2aa773c2819ea1660c45
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: 33340
MD5sum: eaf03e8aa7d259247c4cd6aaf163b003
SHA1: dbcb133b45f1f7a6a1085d2a8935b3b629cadbe6
SHA256: 2242d5471c731f0372c5e0c6eb5f3b47c8f61c6b47b50ce87f85d37541f2145c
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: 23960
MD5sum: b8b1818f17d8cf416b1aa31109f94270
SHA1: 11b74fc2246ad084cb25836e2e55ebbdff7849e2
SHA256: 33bcc4a82e6bcc9edc65783ce2735b3db69675fd645d69d3c17cc4cc0db3ac9e
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: 8920
MD5sum: 2c2c4fb498bc60f3b36578e5084ef4e3
SHA1: c39e8b440003ecdd23d1c51167630282acf5ed14
SHA256: 0e7d054e80e0aec0460d5476b9438a74cab7a2d8618c814018d2495303497239
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.