On Fri, Apr 07, 2006 at 02:16:13PM +0200, Mark Rosenstand wrote:
So, I suggest ignoring the perl version in the footprint like it already happens for kernel modules. Please note that it's the path in the footprint which is ignored, *not* the actual path in the file system. Also note that the purpose is to avoid bogus footprint mismatches in packages with Perl modules, not the perl package itself.
I agree. This already happened with CRUX 2.1 when we had to update perl because of security reasons. Every single port containing something perl-related had to be updated because of the fact that the version is hardcoded in footprints. I don't think I've ever seen a single CPAN module that would be broken by a micro-version update of perl.
This means that when Perl is upgraded, it won't find the modules compiled for the old version (just like it happens now, so our upgrade logic is kept intact.) And as can be witnessed by the attached suggested patch, implemention is trivial.
Yep, looks good to me, makes our lives easier and fits with the KISS principal. I don't see any cons with this, so I give this proposal a +1. // Jukka