On 19 December 2015 at 16:57, David Golden <xdg@xdg.me> wrote: > Author of Module Y updates it to work around Module X's wrap (if they > haven't done so already). > I upgrade Module Y (or re-deploy) to get the fix. > > Alternatively, author of Module::Y can just manually alias a function from X > and nothing breaks when X changes. Its just the problem is fractalic. If you published Z to CPAN, and Z depended "Y => 0", then there will be systems Z encounters with the broken Y => X combination. And so Z itself is broken as soon as it exists in a published state while that combination is possible. And so Z also has to be updated to depend on a newer version of Y, or at least, a newer version of X. And anything(AA) that consumed Z also has this problem. ( depend on a newer version of Z, Y or X ) And anything(AB) that consumed AA also has this problem. ( depend on a newer version of AA, Z, Y, or X ) And this becomes rather annoying when the problem existed in Y for a single release, but for some unknown reason, all the smoke testers installed that without getting a newer exporter. These are the sorts mistakes that are hard to kill once they happen :/ -- Kent KENTNL - https://metacpan.org/author/KENTNLThread Previous | Thread Next