On Fri, 17 Jun 2005 01:14:51 -0700 Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Fri, Jun 17, 2005 at 10:43:14AM +0800, imacat wrote: > This is all a bit of a ramble. Could we have an executive summary as to > the point particularly in relation to MakeMaker, CPANPLUS and module authors > in general?
It's not my question, isn't it? I'm not writing XS modules. I'm
just a poor CPAN tester offering my CPU, my bandwidth, my time testing
new modules and being accused by modules author for sending FAIL reports.
Forwarded by imacat <[EMAIL PROTECTED]>
----------------------- Original Message -----------------------
From: imacat <[EMAIL PROTECTED]>
To: Perl CPAN Testers <[email protected]>
Date: Fri, 17 Jun 2005 09:42:37 +0800
Subject: Re: Failing Reports due to 3rd Party Software (was Fw: Re: FAIL
Convert-Binary-C-0.59 MSWin32-x86-multi-thread 4.0)
----
On Thu, 16 Jun 2005 22:12:50 +0100
"Barbie" <[EMAIL PROTECTED]> wrote:
> However, the conversation thread brings up another issue that has been
> floating
> around for some time. External libraries and apps that are pertinent to a
> successful test suite, may not be available or installed on the smoke box. I
> agree with Robert and Imacat that these should be flagged, so that anyone
> looking at the cpan-testers web pages will know that there isn't a
> straightforward install involved. In my opinion that report should be
> something
> other than FAIL, UNKNOWN or NA, as those have specific meanings. To be
> honest
> I'm not really sure the 'PERL_IS_TOO_LOW' check should be an NA report
> either.
> There needs to some other report type that indicates the build could not
> continue due to external factors. Any "visitors" would then at least know
> that
> they need to read the README, at the very least, to see what extra software
> they
> need. As to what to call this other report I don't know. I've been thinking
> about this for over a year and still haven't thought of anything suitable.
> The
> closest I got was UNGRADED.
From my personal experience dealing with GNU autoconf and automake,
I think the module author should be responsible to specify what external
executables, libraries, versions are required. Then ExtUtils::MakeMaker
can produce a certain error checking them before generating the Makefile,
and CPANPLUS can then capture that error and know some external
prerequisites failures.
I think I was wrong on this issue. This is not only CPANPLUS's
responsibility. ExtUtils::MakeMaker should return certain status or
message to notify CPANPLUS for that.
--------------------- Original Message Ends --------------------
--
Best regards,
imacat ^_*' <[EMAIL PROTECTED]>
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt
<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://www.linux.org.tw/mailman/listinfo/tlug
pgprvuXFtPdJi.pgp
Description: PGP signature
