develooper Front page | perl.perl5.porters | Postings from May 2013

Re: RFC: Deprecating Module::Build

Thread Previous | Thread Next
From:
Leon Timmermans
Date:
May 23, 2013 15:15
Subject:
Re: RFC: Deprecating Module::Build
Message ID:
CAHhgV8j98uu2OO=Q44RyxYCTaos4TG+CPDsRN_Lucv8BRVJQkQ@mail.gmail.com
On Wed, May 22, 2013 at 7:44 PM, David Golden <xdg@xdg.me> wrote:
> I propose deprecating Module::Build from core in 5.19 and removing it in 5.21.
>
> My rationale:
>
> * Module::Build has been in life-support maintainance for a couple
> years now (thank you leont for taking up that awful task)
>
> * CPAN clients have supported configure_requires to bootstrap a build
> tool since Perl 5.10.1 almost a decade ago
>
> * CPAN.pm has support for auto-detecting an undeclared dependency on
> Module::Build and installing it when needed [1]
>
> While many people still use M::B for their modules, it does not need
> to be in core for CPAN modules to depend on it.  Module::Build can be
> removed from core and CPAN clients will install it on demand.

I'm generally in favor of getting stuff out of core. There is no
technical requirement anymore to have this in core.

Assuming about 15% of CPAN uses Module::Build, you'd install it after
on average 4.2 modules, I'm not sure that's an argument for or against
removing from core.

> Given that it is buggy, complex and nearly unmaintained, I don't think
> the core should implicitly be promising support for it.  The fewer
> modules in core, the less work for core maintainers.

I've already chainsawed some modules out of Module::Build, removing it
from core would make it much easier to refactor Module::Build to use
them (as they wouldn't have to enter core).

It would likely also mean removing ExtUtils::CBuilder, which is even
less maintained and buggier than Module Build.

Likewise, Perl::OSType and possibly Module::Metadata could be removed.
This will likely have less of an impact though.

> (Personally, I hope the development of a Build.PL specification [2]
> will encourage new, better successors anyway.)

Working on that!

> If you disagree, now is the time to speak up.  Ideally, if you care
> enough about keeping Module::Build in core, you'll also volunteer to
> take over active maintenance for it, right?  :-)

Yeah, that'd be most welcome!

Leon

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About