Same here.
On 08/04/2005 20:02 Ken Williams wrote:
On Apr 8, 2005, at 12:32 PM, Michael G Schwern wrote:
die "NA: $reason";
Since, at the moment, we're having trouble putting together a system to
cover the possible reasons for an NA report let the module author
figure it
out. Its simple and m
I'm all for something like this, though I prefer "requires_libraries"
instead. (Listing libraries distinct from applications is a grey area,
so best to put them under one term.)
Come to think of it, why not "recommends_libraries" too?
What is needed is some standard set of library and applicatio
Is there a way tests to determine that a module cannot be installed on a
platform so that CPANPLUS or CPAN::YACSmoke can issue an "NA" (Not
Applicable) report?
CPANPLUS relies on module names (e.g. "Solaris::" or "Win32::") but that
is not always appropriate in cases where a module runs on many
FYI, I've uploaded Module::Phalanx100 to CPAN in to
$CPAN/authors/id/R/RR/RRWO/Module-Phalanx100-0.01.tar.gz
It simply contains a list of the Phalanx distributions from the project
web site at http://qa.perl.org/phalanx/.
It's provided so that anyone who needs a consistent list can use it
rath
This isn't a bundle. It just provides a list of modules, though I guess
something could parse the Bundle::Phalanx, thanks.
On 20/03/2005 23:43 Andy Lester wrote:
On Mar 20, 2005, at 4:18 PM, Robert Rothenberg wrote:
FYI, I've uploaded Module::Phalanx100 to CPAN in to
$CPAN/authors/id
I have a prototype Perl script that will determine the dependencies of a given
CPAN distribution, and then check CPAN Testers for any failure reports of that
distro or dependent distros for a given platform.
I would like to work with other people to turn this into something of use to
the community,
I have a prototype Perl script that will determine the dependencies of a given
CPAN distribution, and then check CPAN Testers for any failure reports of that
distro or dependent distros for a given platform.
I would like to work with other people to turn this into something of use to
the commun
On 7/11/2004 12:46 AM Michael G Schwern wrote:
Most modules now have a META.yml file which contains (amongst other things)
module dependency information. Simplest thing to do would be to make a
local miniCPAN mirror [1] and walk through the archive files [2] in
modules/02packages.details.txt look
results for
platform 'x' for a specific module, I can check to see if one of the dependent
modules fail on that platform.
Thanks,
Robert Rothenberg
(FYI, I've just posted a question on PerlMonks regarding this,
http://www.perlmonks.org/index.pl?node_id=373386)
