On Jun 3, 2005, at 8:19 PM, Mich�le Garoche wrote:
Mich�le, This is an issue with Fink's UpdatePOD, not with any individual package. It occurs when you remove the last perlmod for a given version of Perl.� I found this issue a while ago. Fink was actually leaving old *content* in the perllocal.pod when the last perlmod was removed, that's fixed now (HEAD) and we just leave an empty file.�We thought it would be bad to remove the file, because it might unmask another perllocal.pod, so that removing the last pm586 module would cause 'perldoc perllocal' to find pm581 modules now. A brief investigation shows that not to be the case, so maybe it *should* actually be removed.� In any case, it seems to me that 'perldoc perllocal' isn't quite right in any case, because the perllocal.pod for versioned modules masks the perllocal.pod for non-versioned modules. So 'perldoc perllocal' doesn't find my non-versioned modules. This doesn't sound like the right result, but I'm not really sure, can any of our perl experts clear this up? (Hi Randal!) If we're doing the wrong thing here, we can modify the UpdatePOD code to fix things, shouldn't be too hard.
If you have perl581-core installed (it's available in 10.4-trans), why not install pm581 modules? Some modules have still not been tested on 586, there may be some bugs in 586, there may be some program that needs to rely on a versioned perl module and is currently choosing 581, all kinds of reasons why it's good to allow this. It is a little ugly how upgrades to Tiger cause system-perl581 to disappear but leave pm581 modules installed. To be honest I didn't pay much attention to this when I upgraded. Can anybody who did pay attention tell me what Fink did about this case? (Leave the pm's stranded and deps broken, or install perl581 automagically are the obvious possibilities, but I've learned not to expect the obvious with upgrades :-) Thanks for bringing up this issue. Dave |
PGP.sig
Description: This is a digitally signed message part
