Package: deb-perl-macros Version: 0.1-26.2 Architecture: all Maintainer: Victor Zhestkov Installed-Size: 42 Depends: perl Filename: all/deb-perl-macros_0.1-26.2_all.deb Size: 2700 MD5sum: 36d4cbcc94fad87cd599c62a28220da7 SHA1: a4a57c467c5eb908bef41129c01d35413c58f71d SHA256: f634e658beb84a1bce3b80a6a75973f9fa1cd0506d2722701e1411aa2fd50b2f 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: 23.12.0-38.1 Architecture: all Maintainer: debbuild developers 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_23.12.0-38.1_all.deb Size: 54800 MD5sum: 9965332a0de6ec17febabef278928b97 SHA1: 610f0fc325b306a9f1291d106fb023fe1dfee648 SHA256: ba68f261434a50f7b217f49ef42e6b7d4f44056444e9bedd121101cd29b1b7d1 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: 23.12.0-38.1 Architecture: all Maintainer: debbuild developers Installed-Size: 32 Depends: debbuild (= 23.12.0-38.1),liblua-api-perl Filename: all/debbuild-lua-support_23.12.0-38.1_all.deb Size: 8416 MD5sum: 547a78faec0c799ef87825a265051380 SHA1: 95b85fa14014484b8e748f229d6bd7c1c163d507 SHA256: ae17a81ed226f726bd37799a35e99ac2d381ae920db6f6452e833ba5801a1d6a 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-27.1 Architecture: all Maintainer: debbuild developers 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-27.1_all.deb Size: 25500 MD5sum: 4b3d821c73a1843e56207e2dcbd39898 SHA1: 68612eff1b1de6e496e38e2579bfbb0e582a4920 SHA256: 622b0c769fd08724fb6ecb7748689574f8c37f3c3074c345f98032c3432bbb53 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-71.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 401 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: ppc64el/liblua5-1-5_5.1.5-71.3_ppc64el.deb Size: 76856 MD5sum: 525dfa6d1645844cc1e7acdb7e7600de SHA1: f16da9c9a9b0194f01418d22630f9cc98e3ddde6 SHA256: 8cb38328b9d1c677a2b70dcefac210e5f805f55f52769d80e52c0c5c67082852 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: liblua5-1-5 Version: 5.1.5-71.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 359 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: s390x/liblua5-1-5_5.1.5-71.3_s390x.deb Size: 74680 MD5sum: 020abd91e98fb017438615fe92fa93b0 SHA1: c87f722dae7607354ab69a9a3363f90490e1de47 SHA256: 3b5ec168deacd3f4a0bc41561d4f8f943f4f5df76e1c07978283929bc6b781cf 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: liblua5-1-5 Version: 5.1.5-71.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 749 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: armhf/liblua5-1-5_5.1.5-71.3_armhf.deb Size: 281932 MD5sum: 0ecb93d161706369b9a08da629076c32 SHA1: 861c5c4db94e22613e413439c3a48cc5e14cbdff SHA256: 2acb70419d83663b905a54fd0d5447a5fba8890e47583672c276ea3f3acc18da 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: liblua5-1-5 Version: 5.1.5-71.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 862 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: arm64/liblua5-1-5_5.1.5-71.3_arm64.deb Size: 294252 MD5sum: 527f8dfdebab556d077c876c90f11efe SHA1: 1cb8355b63d9898f01d1c1c5172f14258431e89b SHA256: b329e31f037a325b99482bbbd05f901526058d6475d6d7d369782da7a6e59a4d 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: liblua5-1-5 Version: 5.1.5-71.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 857 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: amd64/liblua5-1-5_5.1.5-71.3_amd64.deb Size: 307704 MD5sum: edde74f5313b01e63d4fe19d21e0a35b SHA1: 854de613b2c637e5fe31475bb2fa897395a4aadf SHA256: 8019df6e1915ae91c176fe1c07b48e8bb89e8c94cda664efd0072c43a24b7d20 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: liblua5-1-5 Version: 5.1.5-71.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 804 Replaces: lua51-libs (<< 5.1.5),liblua5-1 (<< 5.1.5-71.3) Provides: lua51-libs (= 5.1.5-71.3),liblua5-1 (= 5.1.5-71.3) Filename: i386/liblua5-1-5_5.1.5-71.3_i386.deb Size: 305972 MD5sum: 5590ebac6a6056adb667349e1807e660 SHA1: fdfeae2b495079df7e0ffdec0a36a027e1b267a1 SHA256: ddb52ab35bd4387563cec54e9b8d9b6052366f105f4dc0b2b0a15ff449390049 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-50.1 Architecture: all Installed-Size: 25 Filename: all/lua-macros_20210827-50.1_all.deb Size: 1480 MD5sum: 15051c6202d178873710df495c1a7895 SHA1: fd45755058cea5dc1e8260fd04a7ab84cfbaa3bb SHA256: 268f97d881656dd0c2c88a5329bca228d906bea339e8828b6bfa000877c81df4 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-71.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 645 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: ppc64el/lua51_5.1.5-71.3_ppc64el.deb Size: 92920 MD5sum: 21c53ef3a9ba996a2ec0547b2b111ac5 SHA1: c31b563632cfab2a5756392ca05d3923c4e46f94 SHA256: a4c0f87e2ea2e130d5378eaf612a240c03e52fb1ed0f4f13495a8f37b0f2a467 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 Version: 5.1.5-71.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 604 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: s390x/lua51_5.1.5-71.3_s390x.deb Size: 89764 MD5sum: a7662fbb1d922992e9e82122aa30f9a7 SHA1: 8aea397df97b71e06efebed559f6ad4e862ee473 SHA256: 9df7b1cfa8089871e4e83c8aa2b9053c931ba8761aec61fb9e43e59cad796caa 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 Version: 5.1.5-71.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1314 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: armhf/lua51_5.1.5-71.3_armhf.deb Size: 345020 MD5sum: d1751d49e5f4d50fc3991a2bc1a8e170 SHA1: 8f8a7aaac645b8555fb77837d637d7f9d942433e SHA256: 74e483a53822a53fbdd9ed1cc87be336f8c2f3fcd178362e6e85bfa9ce18ca79 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 Version: 5.1.5-71.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1510 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: arm64/lua51_5.1.5-71.3_arm64.deb Size: 360532 MD5sum: c9cb51a546919843fcfa5f58dc30e426 SHA1: cc9a3110c091904055744e83e8c3b73c824e371d SHA256: 3ae772ad366658ec7572d4e258f2d9d9cd4c4fa46f0d3c65429490bc0d15c08d 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 Version: 5.1.5-71.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1489 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: amd64/lua51_5.1.5-71.3_amd64.deb Size: 376812 MD5sum: cb73bacfc5b570f0b8f06e6974870d01 SHA1: 4dced00844d14e21578f96e98d599c1a9f450a54 SHA256: 40456f44dc1ac945a9569b131dbb37da265e2231088743b8b6b0ed739864afbf 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 Version: 5.1.5-71.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1413 Depends: dpkg Provides: lua (= 5.1.5-71.3),lua-api (= 5.1) Filename: i386/lua51_5.1.5-71.3_i386.deb Size: 374324 MD5sum: 5fe21144e5449c4f66d45f339cc40c7f SHA1: 95054488114cc12a93ccf234fd3a992b867ba7bd SHA256: 2645b57974e15da3e06adbfe823fcba25b603683605fd65b92c3885d2e1fe636 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-71.3 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 582 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: ppc64el/lua51-devel_5.1.5-71.3_ppc64el.deb Size: 92992 MD5sum: 2b7b76c7ae13cb71d11b3bbaa8a5f22a SHA1: fc25ffe4d41b3c5eba0137d7914792b7561d4691 SHA256: 3b6df91ee2196a07681058445d88c62dce520b1430d6281e343268f163517549 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-devel Version: 5.1.5-71.3 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 561 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: s390x/lua51-devel_5.1.5-71.3_s390x.deb Size: 90216 MD5sum: 8aadc5d195def75bd094a5a48ddaf8e8 SHA1: d5a312178d5c356fc7fdd44a42beb60576c9cb3c SHA256: 7134202bc6ed89b06d3ee5def429c48571f37627a6e7aa3b764b73e1b52c84d8 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-devel Version: 5.1.5-71.3 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 1109 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: armhf/lua51-devel_5.1.5-71.3_armhf.deb Size: 356492 MD5sum: f698938f275e525865a50f9b0c235909 SHA1: 4c4252de67f25b9417a51f2b563a47484423ad19 SHA256: 444672eb14d607f4b44fdb3796d7fb3152bcbc60c34aa3aadc56b0ec7ccdf95b 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-devel Version: 5.1.5-71.3 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 1662 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: arm64/lua51-devel_5.1.5-71.3_arm64.deb Size: 372408 MD5sum: da5cb2bd972795e6528bf25d839dbdd1 SHA1: d9ccbd33097b752df3c3a2d4f91357201c3bdc57 SHA256: 1fa635bb3647810afac6e264f5131d0c12cb45a39f7caa68859a87bc4b4803ff 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-devel Version: 5.1.5-71.3 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 1685 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: amd64/lua51-devel_5.1.5-71.3_amd64.deb Size: 383188 MD5sum: 928296b13f785c1405794c308aa52ba6 SHA1: 5c863fab89f6f8ee16e2a318a1f8346072f7038c SHA256: 403fbef6f44343014c7be632935de0bb7eb9747a1db79bd9318dd200df455082 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-devel Version: 5.1.5-71.3 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 1189 Depends: liblua5-1-5 (= 5.1.5-71.3),lua51 (= 5.1.5-71.3),lua-macros,dpkg Provides: lua-devel (= 5.1.5-71.3),lua-devel (= 5.1),pkgconfig-lua (= 5.1.5-71.3) Filename: i386/lua51-devel_5.1.5-71.3_i386.deb Size: 382052 MD5sum: 9ab1969d15c66c4737c7d1778dc8c393 SHA1: eb358b0e34a397d2b799a6750de52e2b638b36fe SHA256: 01fe58791fc45986604405c7fceb16c2660452356c7129fd1cc8d5e286b9bd15 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-71.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 330 Filename: all/lua51-doc_5.1.5-71.3_all.deb Size: 71672 MD5sum: acdf888d2dbcbb739aaaaa352c608713 SHA1: a32ac00cbfa4934cd6119f03f7c1f5dce1b0b88b SHA256: bc9229f3a7dfe9e5bc90768eb422527bed8368212a58f3ca4e1a35f947a6ea96 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 121 Filename: all/perl-capture-tiny_0.48-26.1_all.deb Size: 30008 MD5sum: 60c474daeb0db9f093404cc88932bafe SHA1: ddf9899acbdef265b251c2d341f62307ba5fbc1c SHA256: d9179204ac31be00f7af9310a472b48bbc544285a838c64f483aa90219750758 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 88 Filename: all/perl-carp_1.50-26.1_all.deb Size: 22672 MD5sum: 178c3d3795fcbbfb4094e9c87d48c4b6 SHA1: aa5334a9b23464ce95e55c97b41010345894ed29 SHA256: 935d7e4f3c5d20ec939486f68e7b77f4e1ba87809531ae2391b793e30f017ced 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 55 Filename: all/perl-class-data-inheritable_0.09-26.1_all.deb Size: 7240 MD5sum: d71a4b9aaca91dd517e95546e42826b1 SHA1: 75380eb8f3e3d213dc135261f149831c6b5f02a1 SHA256: 7e397633e169845a33115f4b8d4660061ee1e21a6f475c121a16d2330d4a757c 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 113 Filename: all/perl-devel-stacktrace_2.04-26.1_all.deb Size: 28404 MD5sum: 30b9145a113d941512607483790d82ae SHA1: c49bf967b6f4d0eb21c1388762b93be8a7b5f58b SHA256: 85e15bd35c7acbb17fdca32e8a63420fce4d55a972d8b4a72a429d136e2e0b42 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 76 Depends: perl Filename: all/perl-devel-symdump_2.18-26.1_all.deb Size: 14376 MD5sum: dc2393885a79c18a6835305c819fe2e9 SHA1: eb9fb49cabd8e85ab13cd736bea9545026220881 SHA256: c201459186f4d8a450cec699e595db38d810a38d4d265fdddb459b94d74ec71e 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 142 Depends: perl-class-data-inheritable,perl-devel-stacktrace Filename: all/perl-exception-class_1.45-26.3_all.deb Size: 39052 MD5sum: c0b26fed553637c0d2a307b2c59fe1b2 SHA1: 2600e7ff61dcbedd2372d44f6a84e5e007ecf09c SHA256: 5c019df4bf2f057e60e9f4b23dca34dbfe0eb966230b7ade8d4792d93b69b10b 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 155 Depends: perl,perl-ipc-cmd,perl-perl-ostype Filename: all/perl-extutils-cbuilder_0.280236-25.7_all.deb Size: 39252 MD5sum: 5453f3a5efc1ddc2e6ff0ab8a55fb4fd SHA1: 341f1c21aa52457e3704c5d6749662d825bdf83e SHA256: 18c232f6b46221910b57af9a149e7616f3e8c2a20659768a0b23458127d3ff0d 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 890 Filename: all/perl-extutils-makemaker_7.66-11.3_all.deb Size: 304516 MD5sum: 2a9eb2142d7d2ef77a1165dfdcd6086c SHA1: d57e3fdd9862a445e9a2188b3b78fa83d0784233 SHA256: 9776374041cfd551d7e41601dff0815d30449d6e9ecc835dae61a32769d508c2 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 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 for details of the design and usage. Package: perl-extutils-pkgconfig Version: 1.160000-26.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: pkg-config Provides: libextutils-pkgconfig-perl (= 1.160000-26.1) Filename: all/perl-extutils-pkgconfig_1.160000-26.1_all.deb Size: 10552 MD5sum: 56f5bd202f501a7e820db42038f1e257 SHA1: f8b83fd2c5d8bb765b7cac8e60ddb2d9dedc0e83 SHA256: b84990ab8198b36236a2f0daa985edd6441b02fc15170dc8092667238e4a350e 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 107 Provides: libfile-path-perl (= 2.180000-26.1) Filename: all/perl-file-path_2.180000-26.1_all.deb Size: 30676 MD5sum: 35cc0da7854fb3f1a5a305b42be7ca90 SHA1: 2e991843a1122033506172ffa11cfdab63ab1022 SHA256: a5adb2f36888329c430c955b8fd285c0f547116b811ac339a091ad526fbfe6c8 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 207 Depends: perl-file-path,perl-parent Filename: all/perl-file-temp_0.2311-26.2_all.deb Size: 53304 MD5sum: 3620ecbab33e585c350e202b3ddf1186 SHA1: 87531e5aff94c534cb0dd8ce31dd0b4a9f48b7c8 SHA256: c87bd04f5c470fabbe79144b2a9961f1d8477658d7f7266fa9d6b36277a36ccd 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 127 Depends: perl Filename: all/perl-ipc-cmd_1.04-26.1_all.deb Size: 33176 MD5sum: f199c89513d17625ca36e9b7bbc59cf9 SHA1: 4bb5c9aec7aec10a096cf97e7c5d64ed8b14a38e SHA256: fdb3e4cc7ffbd9a1db00fa4cd30f701f879a4666bbdcd749ff8c8a497fecbab1 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.40 Architecture: ppc64el Maintainer: Uyuni packagers Installed-Size: 790 Depends: perl-base,liblua5-1-5 Filename: ppc64el/perl-lua-api_0.04-27.40_ppc64el.deb Size: 177080 MD5sum: 5d314e392afd0bbbd9ac69d0d84a4949 SHA1: 4eabfd57d5a8fd39008af9a533900314970a629e SHA256: 1b8517feba916f425ddc2ac7ef2f5253f7a2c314abb362e3aa8cb0e589324a9d 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-lua-api Version: 0.04-27.40 Architecture: s390x Maintainer: Uyuni packagers Installed-Size: 724 Depends: perl-base,liblua5-1-5 Filename: s390x/perl-lua-api_0.04-27.40_s390x.deb Size: 167644 MD5sum: 1fe9a93b939e60dc253f1518982993ed SHA1: 43840fa7450845283c4db26839a981ce4434391e SHA256: 8a55f1eed895facd03c257d59c88dc5b0ccab927f1bedff246924211943ac84b 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-lua-api Version: 0.04-27.40 Architecture: armhf Maintainer: Uyuni packagers Installed-Size: 640 Depends: perl-base,liblua5-1-5 Filename: armhf/perl-lua-api_0.04-27.40_armhf.deb Size: 170004 MD5sum: bfd7f7cfc164f1a8804950a442ea1e8f SHA1: 92ca6203bf443755d67deb22db6b82522925aac2 SHA256: f12c18f520456cf700778269b4d65fedb5d78a0789d61f5eb835887b5bc0dbdd 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-lua-api Version: 0.04-27.40 Architecture: arm64 Maintainer: Uyuni packagers Installed-Size: 750 Depends: perl-base,liblua5-1-5 Filename: arm64/perl-lua-api_0.04-27.40_arm64.deb Size: 167452 MD5sum: a90647aa226d8bfd5f47a24425d59416 SHA1: 7e14e0ff8d83eb1c4c6e071c76e902323151490d SHA256: d4542dc41f87645a11a1c0da8b7a6c0dc0fb5f5336b78043b2997a3c01fa5d82 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-lua-api Version: 0.04-27.40 Architecture: amd64 Maintainer: Uyuni packagers Installed-Size: 702 Depends: perl-base,liblua5-1-5 Filename: amd64/perl-lua-api_0.04-27.40_amd64.deb Size: 173884 MD5sum: d86caf4b12861c5587b4855416b400b7 SHA1: a2855601266b6b15a6120787558012c885a52ed7 SHA256: 73e2441c679e89fce0d0afeede1dc3286821195327d46a94d6f9d51c6abaef69 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-lua-api Version: 0.04-27.40 Architecture: i386 Maintainer: Uyuni packagers Installed-Size: 653 Depends: perl-base,liblua5-1-5 Filename: i386/perl-lua-api_0.04-27.40_i386.deb Size: 162656 MD5sum: dbd4f3fdf47463dfcf6180553fb03a70 SHA1: 7d81fb618b5358115b67653f825c5d803703871e SHA256: e4edb88a3fe65dee8b28176c3f3e4266ba49369f0f2a86516e2b6714219bf6b5 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.4 Architecture: all Maintainer: Uyuni packagers 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.4) Filename: all/perl-module-build_0.423400-29.4_all.deb Size: 251172 MD5sum: ffb826699e2271503aa56549388c2700 SHA1: bd287ddb34eb8c93ad356b6697cf58a4a949153a SHA256: 36fbd78afd7bc161ac9c15ffaf2c88fdc9c4115e87d99802db8d603784e59249 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 111 Depends: perl Filename: all/perl-module-metadata_1.000038-26.1_all.deb Size: 29652 MD5sum: 1e898a2409ce1181b65541a88c88044b SHA1: e8e3739257f6144ef519d12a18e26289a757d93a SHA256: 9ee7767f9093227d8bae7569e5c389809293c585c3d183c27ddb2a84aa8765de 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-module-runtime_0.016-26.7_all.deb Size: 18448 MD5sum: 0b33c82b9bf5a1d95013084e35bdf401 SHA1: ecaf5884cd5dfa33cabccea72251c376e7cb03ee SHA256: 321dca2289266c0e8b350094db8c6897d24846d24f1526be4fa3aaa67138c7dd 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 81 Filename: all/perl-mro-compat_0.15-26.1_all.deb Size: 17196 MD5sum: 6c0c57c02290c0bfca3840775e1d1fb5 SHA1: 26163ea662dc94a15fcec21cd0cc8d33a9077de2 SHA256: c2ce2f7539571d2066741342fe0e586b14252f4141398e9de967785b9d4fb840 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.238-26.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 47 Filename: all/perl-parent_0.238-26.1_all.deb Size: 8356 MD5sum: 033da600ea1969b4360ec49f4dec65d1 SHA1: 29f52052141102852d1ee62fa7ed26e217b4d49d SHA256: f0fd698fa0ecb2adfcd186421332e00de1908ff5a800e49e7f99b39f3e5ce086 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 74 Filename: all/perl-perl-ostype_1.010-26.3_all.deb Size: 15200 MD5sum: d17ec5e517fba48560c4a76292b8d11a SHA1: 36299c708c64b9c8fedc5cf040e89180e5cddb8e SHA256: c5e5aea333c613d7cd52ae7c0c10ad74940a03add11670345445fbba9ea6c861 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.4 Architecture: all Maintainer: Uyuni packagers Installed-Size: 85 Depends: perl-devel-symdump,perl Filename: all/perl-pod-coverage_0.23-28.4_all.deb Size: 19132 MD5sum: cd14edeb124b1cff462b043e6db4ee8e SHA1: c8ea4bf51bd1bee440591c67e8dca6606ca602d3 SHA256: 8f854a3bc76062af206c79421d2687f84caa782bcc91de75ef94cecbf85eea0f 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.16 Architecture: all Maintainer: Uyuni packagers Installed-Size: 112 Filename: all/perl-sub-uplevel_0.2800-25.16_all.deb Size: 22176 MD5sum: 79252326286bf40213f0e52c32fce3f5 SHA1: 9ccb4b9f4bbd612ef4f9035d66425558ff835240 SHA256: 1861fa08124dbecc68778677449e7fe28a5480ab18f41df4a17072257878243a 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.10 Architecture: all Maintainer: Uyuni packagers Installed-Size: 208 Depends: perl-mro-compat,perl-module-runtime,perl,perl-try-tiny Filename: all/perl-test-class_0.52-26.10_all.deb Size: 56808 MD5sum: a37b101c479bff36e1a41a91faf49fe9 SHA1: 5c2390b7f21ece7c816b89ded154bceb79ab8c5f SHA256: 4d212f0cbf7d2b2c86e41da197f768adf8ba1b5f03802d8301f5b4547e75c0d9 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.5 Architecture: all Maintainer: Uyuni packagers Installed-Size: 86 Depends: perl-base,perl-parent Provides: libtest-compile-perl (= 3.3.1-26.5),libtest-compile-internal-perl (= 3.3.1-26.5) Filename: all/perl-test-compile_3.3.1-26.5_all.deb Size: 21456 MD5sum: 740888de299cf37b8004d682efa50845 SHA1: ab465d6b623d50cea26eafd227fd7645b7fd1454 SHA256: 8c8e7b8e880506108045a506a4fd4fcdc0a134b4496d7df931732798b7b7610a 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.2 Architecture: all Maintainer: Uyuni packagers Installed-Size: 353 Depends: perl Filename: all/perl-test-deep_1.204-27.2_all.deb Size: 93292 MD5sum: d440309bf1cefb45bbfe1b4f67425404 SHA1: 444286d1aa509d5ac355784c2b2aca914f5c4239 SHA256: 2034a8f9fca25e8d4f4d63fda1ef079ce27f1e578c4b8f79dbc694167a0c0869 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.3 Architecture: all Maintainer: Uyuni packagers Installed-Size: 73 Depends: perl-capture-tiny,perl,perl-text-diff Provides: libtest-differences-perl (= 0.710.0-26.3) Filename: all/perl-test-differences_0.710.0-26.3_all.deb Size: 18376 MD5sum: b8414cc401a6e20f2ad641fd58df2364 SHA1: 3bcb33c6e96e66f8d80436112018d69381e102ab SHA256: b6b40104e60d3d2af3f206fadc9a19ff7abe5bc5c458421dc3da35b8e188d4eb 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.6 Architecture: all Maintainer: Uyuni packagers Installed-Size: 71 Depends: perl-sub-uplevel,perl Provides: libtest-exception-perl (= 0.430000-26.6) Filename: all/perl-test-exception_0.430000-26.6_all.deb Size: 18084 MD5sum: 835b0cd57fb9668b86da284d7c27cab0 SHA1: 5e80ed24d5ab38f4db2632c31c6624dd01742a69 SHA256: 021fc989cee99120c279c71b6046ecfd0e90a7b33aebb196f4d9207f4b9f14f3 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 = ; 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.12 Architecture: all Maintainer: Uyuni packagers Installed-Size: 87 Depends: perl-exception-class,perl-test-deep,perl-test-differences,perl-test-exception,perl,perl-test-warn Filename: all/perl-test-most_0.38-26.12_all.deb Size: 23424 MD5sum: 7d8711a887eae74726d10d60bed87a4b SHA1: 83f2d021db9620108ac90d62d52e42ba9e77ab9c SHA256: eae33bd6111899aacec1e20e7d5f32e82f834fc39513f09e14e7b840b69b0dba 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 62 Depends: perl Filename: all/perl-test-pod_1.52-26.1_all.deb Size: 13316 MD5sum: 4d58563aa5507be876cee74c2a1c1475 SHA1: 7d2a22f10617f2203a4b8595a06caab258cabacb SHA256: 509ba6bdc6ab21bfa2a06db5147f3c7167d82dc4f6c2b9b6aa9fa8e5ea94abd5 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.8 Architecture: all Maintainer: Uyuni packagers Installed-Size: 61 Depends: perl-pod-coverage Filename: all/perl-test-pod-coverage_1.10-27.8_all.deb Size: 10940 MD5sum: 7928498780b1df24cc470db4d69722ad SHA1: b22c482d1598d4f272abae694c006f3485c329bb SHA256: 12eb3714f23a890e3e56601cf25ee1614e18db4932495a0c8d8bc6d3c2b8c318 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.7 Architecture: all Maintainer: Uyuni packagers Installed-Size: 70 Depends: perl-carp,perl-sub-uplevel Filename: all/perl-test-warn_0.37-26.7_all.deb Size: 14840 MD5sum: dbce8609d74ae56609da22dec16f451a SHA1: 417f0f6fb7db0cee400a3550cc9043b99e35d3ad SHA256: 9af6a959b0f7faf465a6a061cbe8e5f16e05e671955f3e84a18ebba0db9d6575 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 129 Depends: libalgorithm-diff-perl Filename: all/perl-text-diff_1.45-26.1_all.deb Size: 33344 MD5sum: b57c8732a2daef46e13820675ba348a7 SHA1: 60f1c6a427b70611068b5a3f9e9511aee6ea7c82 SHA256: 2010f7180ca599b3afce293ff57884480297d53db43f255dd6601d572474e1ce 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 80 Filename: all/perl-try-tiny_0.31-26.1_all.deb Size: 23964 MD5sum: 13ac8f7c1b791b029bfc85d4db615dee SHA1: f606e3edf41ad55a65c418f494187457a4ccc98f SHA256: 3441a121d2b581649d5eb73fabbf89b455409737de3fef6eb1710a939a51ab88 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.1 Architecture: all Maintainer: Uyuni packagers Installed-Size: 52 Filename: all/perl-universal-require_0.19-26.1_all.deb Size: 8920 MD5sum: a5a3667b9a100117198a52a9c1a8f9ca SHA1: 2af6a8376e627e8340e0062a9dceb798202f64dd SHA256: 1e2554112f14567ef08ac1c71f7825983ccb838b88980a1e76954d423e9dfebf 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.