From: Andreas K. Hüttel
Signed-off-by: Andreas K. Hüttel
---
eclass/perl-module.eclass | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/eclass/perl-module.eclass b/eclass/perl-module.eclass
index 20b9947caca..81f79992d76 100644
--- a/eclass/pe
From: Andreas K. Hüttel
Signed-off-by: Andreas K. Hüttel
---
eclass/perl-functions.eclass | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/eclass/perl-functions.eclass b/eclass/perl-functions.eclass
index e7775f31b8e..e6168a07534 100644
--- a/eclass/perl-functions.
From: Kent Fredric
These are already committed to tree [ :( ] just relaying to the list
for added oversight/feedback and to make sure any EAPI7 specific
changes like BROOT/BDEPENDS etc get checked off before widespread usage
starts happening.
Any follow-up submissions will be relayed to the list
From: Kent Fredric
@DEFAULT-ASSUMED allows eclasses to document any implied value
that internal code will assume when the ENV var is undefined.
@DEFAULT-ASSUMED should typically be used in conjunction with
@DEFAULT-UNSET, but it can be used in conjunction with either
@DEFAULT-VALUE or normal val
From: Kent Fredric
@DEFAULT-VALUE allows eclasses to document the default values they
will inject when eclass-to-manpage can't extract it.
When eclass-to-manpage *can* extract it, it adds a warning when
the extracted value is different from that declared, (but the
declared value still takes prec
From: Kent Fredric
@RETURNS is abused presently both as bash exit code values ( that
is, bash return values ), and capturable STOUT values.
This is problematic, as they're not equivalent: One is passed
around via $? , and the other requires VAR=$(func) to capture.
Additionally, functions can ha
From: Kent Fredric
---
eclass/perl-functions.eclass | 75 +++-
1 file changed, 74 insertions(+), 1 deletion(-)
diff --git a/eclass/perl-functions.eclass b/eclass/perl-functions.eclass
index 1652ceaa10..9eed888f75 100644
--- a/eclass/perl-functions.eclass
From: Kent Fredric
---
eclass/perl-functions.eclass | 19 +++
1 file changed, 19 insertions(+)
diff --git a/eclass/perl-functions.eclass b/eclass/perl-functions.eclass
index 3f73ac87c7..1652ceaa10 100644
--- a/eclass/perl-functions.eclass
+++ b/eclass/perl-functions.eclass
@@ -4
From: Kent Fredric
---
eclass/perl-functions.eclass | 18 ++
1 file changed, 18 insertions(+)
diff --git a/eclass/perl-functions.eclass b/eclass/perl-functions.eclass
index 027cb0cf7e..3f73ac87c7 100644
--- a/eclass/perl-functions.eclass
+++ b/eclass/perl-functions.eclass
@@ -43
From: Kent Fredric
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)
From: Kent Fredric
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 i
From: Kent Fredric
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
From: Kent Fredric
Greetings,
Following are a series of suggested utilities I want to add to
perl-functions.eclass and additional eyes and feedback are desired
before I finally commit them.
Included are 3 utilities for varying levels of detail in querying
the status of installed Perl Modules fr
13 matches
Mail list logo
