Re: [Module::Build] PERL_MM_USE_DEFAULT

[Yitzchak Scott-T. <sth...@ef...>]

On Thu, Apr 06, 2006 at 08:17:24PM +0200, demerphq wrote:
> On 4/6/06, Randy W. Sims <ml...@th...> wrote:
> > Yitzchak Scott-Thoennes wrote:
> > > On Tue, Mar 07, 2006 at 05:33:49AM -0500, Randy W. Sims wrote:
> > >
> > >>Sorry for responding late to this, but won't this break exististing
> > >>distributions? Distros that currently use y_n() without defaults will
> > >>start die-ing when users upgrade M::B.
> >
> > > It doesn't break them in the sense that they were already broken for some users.  But maybe it would be better to pick an arbitrary default?
> >
> > I don't think there is a reasonable default. I think the only way around
> > the issue is to create new methods and deprecate the older ones or not
> > require defaults. It's not reasonable to have Build scripts failing just
> > because a user upgrades to a new version of Module::Build.
> >
> > This needs to be resolved before 0.28. Any other ideas for solutions?
> 
> Maybe sse the "version trick".
> 
> IOW, if the user says
> 
>    use Module::Build VERSION;
> 
> then you kick in the special behaviour (dying if no default). If they
> dont then you leave it.

The problem that I tried to address is module authors not giving a
default and not realizing that this dies when you try to do an
unattended install.  I want to force a default so they don't have
the option to unknowingly cause some users a problem.