For what it's worth, my logic back then was:
As pointed out here, if Apple upgrades perl, you have probably to upgrade XS modules. But what I was thinking was that there might be an application which embeds perl and therefore links against the perl library. A new system update with a new perl may require that application to relink as well, if it uses API that changed in perl. However, if the API was compatible, the app could continue to work. This will never work, however, if the perl library moved location, as that will cause a linker failure at runtime. So my theory was that breaking less often would be a good thing.
Anyway, this can still be done with symlinks, and perhaps that's a more flexible way to do it.
-wsv
On Monday, December 9, 2002, at 12:05 PM, Christopher D. Lewis wrote:
I did file a bug via http://www.apple.com/macosx/feedback and subsequently, wsanchez apparently submitted a perl patch which leads to version-numbers in the pathname.
--Chris
