On Tue, Sep 30, 2008 at 04:23:53PM +0200, Johan Vromans wrote:
> Michael G Schwern <[EMAIL PROTECTED]> writes:
>
> > Module::Install is the greatest threat to CPAN stability.
>
> So why not get rid of it?
>
> If it does not provide any relevant functionality that EU::MM and M::B
> also provide, it should be possible to convince the author to withdraw
> it.
It provides relevant functionality that isn't available on EUMM any other
way and is very easy to extend - for example, Catalyst apps use a
Module::Install::Catalyst to do some extra stuff that we used to do via
a Module::Build trick but proved kinda fragile due to the Module::Build
dependency problem.
As Adam notes, once configure_requires is widely deployed this becomes a
lot less important - but some of us -do- still like make, for all its evil :)
--
Matt S Trout Need help with your Catalyst or DBIx::Class project?
Technical Director http://www.shadowcat.co.uk/catalyst/
Shadowcat Systems Ltd. Want a managed development or deployment platform?
http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/servers/
