On Mon, Oct 22, 2001 at 09:48:56PM -0400, Michael G Schwern wrote:
> It then orders them in terms of which needs to be installed first. In
> Test::SDK it would be Test::Harness, Test::Simple and finally
> Test::Inline.
since the CPAN Bundle lets you specify exact versions, the purpose
of SDK currently seems to be mostly about simplifying download
(i.e. one big file). while this along is fine, it should arguably
be a integrated utility (i.e. sidekick) that lets you construct
one easily from an existing bundle (and apply to ISPs, etc), rather
than putting the duplicated distributions on CPAN.
but then, i could be totally mistaken.
> Then each module is individually tested and installed in turn. Before
> performing the test & installation it first checks that there's not
> already a higher version installed.
> If any one fails the sequence stops.
does it means if a higher version of Test::More installed, it will
not try to install Test::Inline anymore?
> This shouldn't be too much extra work to pull off. The only unknown
> I'm pondering is if it's worth trying to wedge this into the usual
> "perl Makefile.PL; make; make test; make install" sequence or to just
> have a simple "installsdk" program that gets run.
you'll probably need a stronger ExtUtils::MakeMaker that understands
CPAN.pm. i've been using my ExtUtils::AutoInstall to achieve similiar
ends, also operating in a SDK-like environment (where the CPAN build
directory, passed via -config, is just '.').
cheers,
/Autrijus/
PGP signature
