On 8/18/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > > # from Adam Kennedy > # on Friday 17 August 2007 05:23 am: > > >This is the main reason Module::Install went with the bundle-only, > > because you can't necesarily trust the APIs to never ever change > > (granted, we took advantage of that more than we otherwise might > > have). > > Perhaps we can check some variable in the installed M::B which indicates > an incompatible change to the API? Similarly, the installed M::B might > be able to tell the bundled version that the bundled version won't > work. > > >Personally, I think that the configure_requires is the best fix for > > this problem. > > For the CPAN clients, yes. There is something to be said for an > independently usable tarball though (but I would guess that this > use-case could be satisfied in another way (e.g. a simplified sort of > local cpan mirror.))
Yes, I think there are better ways to deal with this. pip is one example, although it's not good enough yet. --Eric > -- > "Everything goes wrong all at once." > --Quantized Revision of Murphy's Law > --------------------------------------------------- > http://scratchcomputing.com > --------------------------------------------------- >
