On Aug 17, 2007, at 2:37 PM, Eric Wilhelm wrote:
# from Eric Wilhelm
# on Friday 17 August 2007 12:12 pm:
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.
Hmm... Even in the normal use-case, I think we're tied into permanent
reverse-compatibility unless we do something like ship an "old api"
layer with every new version.
Yeah, basically the whole perl world operates under the assumption
that new versions of modules are backwards compatible with old
versions. For M::B in particular we always have to keep backcompat
at the fore. Bundling doesn't change that.
Undocumented features excepted, of course.
-Ken
