Front page | perl.perl5.porters |
Postings from May 2013
On Thu, May 23, 2013 at 4:16 PM, Leon Timmermans <fawaka@gmail.com> wrote: > On Thu, May 23, 2013 at 11:16 PM, Paul LeoNerd <leonerd@leonerd.org.uk> > wrote: > > Ahh.. Yes; that part starts to feel tricky now. > > > > Does the whole of its dependency tree know quite clearly that it cannot > > use M::B at all then? Is this something that can somehow be enforced, > > or at least smoke-tested on? > > A few months ago File::Temp suddenly switched to Module::Build (see > #84531), it broke stuff and was noticed after some time. > > It wasn't sudden really, in that the repository had been using Module::Build for a couple of years. It was sudden in the sense that I didn't tell anyone about it. This was because I was under the mistaken impression that Module::Build was the recommended way of distributing modules these days and that MakeMaker was effectively deprecated (that's that sense I got a few years back). I've been conscientiously migrating all my modules over to Module::Build and now I find that I should have left them with MakeMaker (or gone crazy and adopted Dist::Zilla). I hadn't considered the problem of Module::Build needing File::Temp and File::Temp needing Module::Build. -- Tim JennessThread Previous | Thread Next