On Mon, Oct 15, 2001 at 10:38:25PM -0500, Ken Williams wrote:
> Thanks for Cc-ing me on this, Dave - I'm not subscribed to the 
> module-authors list.  I probably should be.

thanks for your prompt response. :) i was a bit frightened by the
lack of activity on this list.

> There's not any great way around that as far as I know - you just have to 
> fail if your AutoInstall module isn't installed, asking people to install 
> that first.

sure I could add this one-liner on top of modules?

eval "use ExtUtils::AutoInstall;1" or eval "use CPAN; install('ExtUtils::AutoInstall)";

but better diagnosis might be needed...

> That's right - an ambitious goal, though. ;-)  I could use help if anyone 
> wants to offer it.

some test report's here, then. (against Module::Build 0.02)

cpan> install Module::Build

<skip>
/usr/bin/perl -Iblib/arch -Iblib/lib -I/usr/local/lib/perl5/5.6.1/i386-freebsd
              -I/usr/local/lib/perl5/5.6.1 Build.PL Build
Too early to specify a build action 'Build'.  Do ./Build Build instead.
*** Error code 255

a little inspecting revealed that if you add a 

    shift(@ARGV) if $ARGV[0] eq 'Build' # accomodate with CPAN autoinstall

inside Build.PL, then everything'd be happy.

I envision ExtUtils::AutoInstall to be equally applicable on Module::Build
and EU::MM; I'll integrate the features where M::B provides an API.

since you praised cons in M::B's POD, one may very well wonder why you don't
use cons (as a dependency or auto-fetch) and write a Construct script from M::B,
instead of re-implementing low level functions by yourself. are there any
design reasons?

thanks,
/Autrijus/

Attachment: msg00162/pgp00000.pgp
Description: PGP signature

Reply via email to