Dave The one thing here you need to remember, even if you don't know how it all works, is that some of the toolchain features work (conceptually) very different depending on whether they are the core or not.
configure_requires being the standout example, it would be completely compromised and largely pointless if it only existed outside the core, because you could never bootstrap yourself up to supporting it. So if someone who owns one of the pieces of the toolchain says the REALLY want something patched, it's usually for reasons like this. Because that patch is 80% or 90% less useful if it's stuck outside. Adam K 2009/8/10 Dave Mitchell <da...@iabyn.com> > On Sat, Aug 08, 2009 at 11:41:08AM -0400, David Golden wrote: > > It wouldn't be the first time a dev module was released in core. :-) > > If I recall, 5.10.0 had a version of Module::Build that didn't even > > exist on CPAN. > > > > I was hoping to get to a release version of M::B for 5.10.1, but Dave > > M seems to have said "no more dual-life integration". > > > > Dave M -- this one might be worth a quick patch. Let me know what you > > want me to do about it. > > Well, I've understood practically nothing in this thread so far > (ExtUtil::*, CPAN*, Module::* etc are a total mystery to me), but... > > given that it looks like I'll need an RC2 for the configure stuff anyway, > and if your suggested change is just a version bump with no other > non-cosmetic alterations, then I suppose yes! > > -- > Any [programming] language that doesn't occasionally surprise the > novice will pay for it by continually surprising the expert. > -- Larry Wall >
