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. > Dependency-creep happens, sometimes in nonobvious ways, that lead to > cyclic dependencies or other weird breakages - any non-core build > system feels like it could be much more prone to gaining one of these > by accident. This kind of problem is fairly inherent to client-side toolchain stuff. We have to be leaner on dependencies than other people out of necessity, not out of choice. LeonThread Previous | Thread Next