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 "req
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 al
On Apr 7, 2005, at 8:28 AM, Reinhard Pagitsch wrote:
Hello Chris,
Chris Dolan wrote:
On Apr 6, 2005, at 11:06 AM, Reinhard Pagitsch wrote:
I would suggest now to name the module
Win32::Storage::ReadSummaryInfo.
I like this better than before, but why not
Win32::Document::SummaryInfo?
Because not
Chris Dolan wrote:
On Apr 6, 2005, at 11:06 AM, Reinhard Pagitsch wrote:
I would suggest now to name the module Win32::Storage::ReadSummaryInfo.
I like this better than before, but why not Win32::Document::SummaryInfo?
It seems to me that if the module deals with what Windows calls
"Properties",
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 al
On Apr 6, 2005, at 11:06 AM, Reinhard Pagitsch wrote:
I would suggest now to name the module Win32::Storage::ReadSummaryInfo.
I like this better than before, but why not
Win32::Document::SummaryInfo?
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1
