# from A. Pagaltzis
# on Friday 20 April 2007 10:34 am:
>As far as I’m concerned, `configure_requires` is the solution
>that should have been implemented IN THE FIRST PLACE.
Yep. That about says it all. That, and a client that checks for the
need to update whenever if fetches the module list.
>> This STILL doesn't fix the problem with current or old default
>> Perl installations without upgraded CPAN clients, but then you
>> REALLY can't fix a circular dependency that only occurs due to
>> events that occured in the past.
>
>That should be possible to fix, shouldn’t it? What I’m thinking
>is Module::Build::Installer which implements just enough of
>CPAN.pm to recursively download, install and run Module::Build
>using the existing CPAN::Config, so that you could depend on
>Module::Build::Installer in a sort-of passthru Makefile.PL.
Well, the trouble is that you're not always installing under the CPAN
client. Unfortunately, the old CPAN.pm doesn't leave any sort of
environment variable or other hint for the subprocess. Thus, we can't
really tell whether we're in CPAN* or some other batch job. So, we may
not have network connectivity, etc.
`ps ax --forest` would tell us something, but of course that's only on
the real operating systems. Of course, there's not much a subprocess
can do without embedding some kind of huge mess in every distribution.
So, the old CPAN* clients are broken.
Maybe if we just talk about it enough, everyone will upgrade to a
working client? Start a security scare? Or, hey. Change the format
of the 03modlist.data.gz.
--Eric
--
Hot dogs: just another condiment.
--Heart-attack Man
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
