On 07 April 2005 23:02 Ken Williams wrote:
On Apr 6, 2005, at 7:13 AM, Robert Rothenberg wrote:
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
Chris Dolan wrote:
On Apr 6, 2005, at 7:13 AM, Robert Rothenberg wrote:
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
David Cantrell wrote:
Let's take my module File::Find::Rule::Permissions as an example. I
know it doesn't work on Windows, but not having access to a Windows
machine, I have *no idea* what $^O should be on that platform,
especially for any odd Windows environments like Cygwin or WinCE. I
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
On Apr 6, 2005, at 7:13 AM, Robert Rothenberg wrote:
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
On Apr 6, 2005, at 7:13 AM, Robert Rothenberg wrote:
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
On Thu, Apr 07, 2005 at 05:01:34PM -0500, Ken Williams wrote:
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?
AFAIK NA reports are issued when a Makefile.PL dies due to a require
