On Feb 11, 2008, at 5:01 PM, David Golden wrote:
On Feb 11, 2008 6:52 PM, brian d foy <[EMAIL PROTECTED]> wrote:
That's not really true. Although I use CPAN::Shell for some things,
cpan isn't just passing things along. My program is a different
interface using the same backend.
Right -- you're not handing off all arguments to CPAN::Shell at once.
However, I think he wanted CPAN.pm to halt if any *dependencies*
failed as well as anything specified to the "cpan" script -- that
requires a change to CPAN.pm, not just the queue in "cpan".
Yes - that is the desired behavior (I'm working with Andrew on this
and asked him to post here.)
We want the entire build to stop and fail if any of the dependencies
fail during testing or installation.
We are creating a build script that handles building a complex
collection of modules, some locally created, some from the public
CPAN, there are many dependency and other issues (such as needing to
create distro_prefs files at build-time to answer questions posed by
XML::Parser and others.)
-M
-------------------------------------------------------
Matisse Enzer <[EMAIL PROTECTED]>
http://www.matisse.net/ - http://www.eigenstate.net/
