On 13/12/2007, David Golden <[EMAIL PROTECTED]> wrote: > > On Dec 12, 2007 5:22 PM, Adam Kennedy <[EMAIL PROTECTED]> wrote: > > A->B) Dependencies are determined by running Build.PL > > > > B->A) Build.PL has a dependency on Module::Build. > > > > The code used to determine dependencies itself has a critical dependency > it > > can't work without. > > Didn't this get fixed by Module::Build using its own 'lib' directory > in Build.PL?
The problem is NOT that Module::Build can't install itself. The problem is that nobody that USES Module::Build can declare a dependency on it. Core'ifying it in 5.10 will be a partial solution (moves the problem from "can't install" to "can't upgrade"), and configure_requires will be a full solution, but BOTH of these do not provide forward-compatibility for legacy Perl versions (where "legacy" is defined as including 5.8.8). Adam K
