Fwd: [Module::Build] Re: something broken between Module::Build, CPAN.pm, and ExtUtils::MakeMaker in 5.8.8 for UINST=1

[demerphq <dem...@gm...>]

---------- Forwarded message ----------
From: Adam Kennedy <cp...@al...>
Date: Feb 17, 2006 6:11 PM
Subject: Re: [Module::Build] Re: something broken between
Module::Build, CPAN.pm, and ExtUtils::MakeMaker in 5.8.8 for UINST=3D1
To: per...@pe...


Nicholas Clark wrote:
> On Wed, Feb 15, 2006 at 12:07:02PM +0100, Rafael Garcia-Suarez wrote:
>> On 2/15/06, Adam Kennedy <cp...@al...> wrote:
>>> But MB is going to go core real soon now though right? 5.8.9?
>> It's planned for the next 5.9, but I doubt new modules will go in the
>> maintainance track. (But I'm no authority on maint:)
>
> Well, I was assuming that it would be in current stable when current stab=
le
> is 5.10 :-)
> (ie no, not 5.8.x, for the reasons below)
>
> On Thu, Feb 16, 2006 at 07:26:47PM -0800, Yitzchak Scott-Thoennes wrote:
>> On Thu, Feb 16, 2006 at 02:07:50PM +0100, Rafael Garcia-Suarez wrote:
>
>>> On the other hand, if we begin to ship M::B with stable perls, a lot
>>> of people will keep perl's M::B and not upgrade it. So we'd better be
>>> sure it's pretty stable in terms of functionality and API. So I agree
>>> with you here.
>> Um.  Those same people aren't likely to install M::B in the first place.
>> I don't see how providing them with it (even if it will fall out of date=
)
>> hurts.
>
> It won't hurt them, but it will cause immense pain for anyone wanting to
> ship a module that uses a Build.PL - those developers will be forced to
> decide whether to cut out anyone with an old Module::Build, or code their
> Build.PL to use that version and work around the deficiencies.
>
> The thread on what YAML version Module::Build needs, and how to upgrade
> correctly if there isn't >=3D0.50 suggests that solving these "Module::Bu=
ild
> needs upgrading" issues isn't yet battle tested.

Indeed, for example I just installed the new Vanilla Perl and following
the "you need the latest toys" tried to install Bundle::CPAN, which both
installs YAML 0.58 then seems to have a bunch of Module::Build things
fail because it wants < 0.50.

So for now CPAN.pm is seemingly not upgrading properly any more either
on Win32 at least. Or at least you can't install Build.PL-only modules
on Win32, once you hack your way past the Bundle installation problems.

I actually suspect the final solution will be to make Module::Build do a
limited version of the Module::Install trick and bundle just enough code
to boot up and check to see if Module::Build needs upgrading first.

Compulsory upgrading of the installation infrastructure seems the norm
in a lot of places.

Adam K


--
perl -Mre=3Ddebug -e "/just|another|perl|hacker/"