| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
And use @CODE examples where relevant instead as per
eclass-to-manpage.awk
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This utility provides informational data describing the given module
names state of installation, either as a version, or as an error
message describing the grade of failure incurred in module loading.
It has the side effect that it most load the module (and its
dependencies) into memory to give a report value, and can be expensive
and have side-effects from Perl code execuring while the module loads,
including (but not limited to) people calling POSIX::_exit
This is the slowest way of inspecting state about a module, as
it must load the module
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a utility for runtime checking if a module of a given version
is installed from the perspective of Perl, whos opinion could be
different than portage in the event of perl-core/* dual life effects
shortly after a major Perl upgrade.
Use this only if perl_has_module is insufficient, as the overheads
and risk of side effects from this approach are high, given the module
has to be actually loaded for the version comparison to happen.
exits "true" if Perl has the given module installed at the given
version ( or later ), exits "false" otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an incredibly fast way to check if Perl considers a module
of the given name installed in any capacity, including broken.
As long as "Foo.pm" is somewhere in @INC, `perl_has_module Foo` will
return true.
Even `perl_has_module threads` will return true on non-threaded perls,
due to that module still being present, and the module only fataling
when loaded.
Whereas `perl_has_module_version threads 0` will always fail on
non-threaded perls.
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
|
| |
|
|
|
|
| |
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
| |
|
| |
|
|
|
|
| |
.packlist files and keep/fix them in EAPI=6
|
| |
|
|
|