How to Install and Uninstall libmodule-install-authorrequires-perl Package on Kali Linux
Last updated: November 07,2024
1. Install "libmodule-install-authorrequires-perl" package
Please follow the guidance below to install libmodule-install-authorrequires-perl on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
libmodule-install-authorrequires-perl
Copied
2. Uninstall "libmodule-install-authorrequires-perl" package
Please follow the step by step instructions below to uninstall libmodule-install-authorrequires-perl on Kali Linux:
$
sudo apt remove
libmodule-install-authorrequires-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libmodule-install-authorrequires-perl package on Kali Linux
Package: libmodule-install-authorrequires-perl
Version: 0.02-1.1
Installed-Size: 29
Maintainer: Debian Perl Group
Architecture: all
Depends: libmodule-install-perl, perl:any
Size: 10532
SHA256: fbbafa22ec13bc3d029daec422a4618edda31d8000dce63787834aa04fb6ab2e
SHA1: db702999a1580d9930fb4bba5c98d1141910bdfc
MD5sum: 5dd0480225f56a89be2d263c17f6eb70
Description: declare author-only dependencies
Modules often have optional requirements, for example dependencies that
are useful for (optional) tests, but not required for the module to
work properly.
.
Usually you want all developers of a project to have these optional
modules installed. However, simply telling everyone or printing
diagnostic messages if optional dependencies are missing often isn't
enough to make sure all authors have all optional modules installed.
.
Module::Install already has a way of detecting an author environment,
so an easy way to achieve the above would be something like:
.
if ($Module::Install::AUTHOR) {
requires 'Some::Module';
requires 'Another::Module' => '0.42';
}
.
Unfortunately, that'll also make the optional dependencies show up in
the distributions "META.yml" file, which is obviously wrong, as they
aren't actually hard requirements.
.
Working that around requires a considerable amount of non-trivial
Makefile.PL hackery, or simply using Module::Install::AuthorRequires's
"author_requires" command.
Description-md5:
Homepage: http://search.cpan.org/dist/Module-Install-AuthorRequires/
Tag: devel::lang:perl, devel::library, implemented-in::perl
Section: perl
Priority: optional
Filename: pool/main/libm/libmodule-install-authorrequires-perl/libmodule-install-authorrequires-perl_0.02-1.1_all.deb
Version: 0.02-1.1
Installed-Size: 29
Maintainer: Debian Perl Group
Architecture: all
Depends: libmodule-install-perl, perl:any
Size: 10532
SHA256: fbbafa22ec13bc3d029daec422a4618edda31d8000dce63787834aa04fb6ab2e
SHA1: db702999a1580d9930fb4bba5c98d1141910bdfc
MD5sum: 5dd0480225f56a89be2d263c17f6eb70
Description: declare author-only dependencies
Modules often have optional requirements, for example dependencies that
are useful for (optional) tests, but not required for the module to
work properly.
.
Usually you want all developers of a project to have these optional
modules installed. However, simply telling everyone or printing
diagnostic messages if optional dependencies are missing often isn't
enough to make sure all authors have all optional modules installed.
.
Module::Install already has a way of detecting an author environment,
so an easy way to achieve the above would be something like:
.
if ($Module::Install::AUTHOR) {
requires 'Some::Module';
requires 'Another::Module' => '0.42';
}
.
Unfortunately, that'll also make the optional dependencies show up in
the distributions "META.yml" file, which is obviously wrong, as they
aren't actually hard requirements.
.
Working that around requires a considerable amount of non-trivial
Makefile.PL hackery, or simply using Module::Install::AuthorRequires's
"author_requires" command.
Description-md5:
Homepage: http://search.cpan.org/dist/Module-Install-AuthorRequires/
Tag: devel::lang:perl, devel::library, implemented-in::perl
Section: perl
Priority: optional
Filename: pool/main/libm/libmodule-install-authorrequires-perl/libmodule-install-authorrequires-perl_0.02-1.1_all.deb