Just some comments from another Mac user who's never felt any need to install his own Perl ...
>> 1. Most importantly, I don't bugger up the system Perl inadvertently, >> thereby bringing the rest of my work to a standstill. > > Maintaining your own perl module/lib prevents this > problem (that is why this is the solution when one > doesn't have rw access to system files and directories). There's absolutely no need to do that. Apple's Perl is set up out of the box to install modules into /Library/Perl/ and scripts into /usr/local/bin. Thus, there is no danger of breaking the original Perl installation, which resides in /System/Library/Perl. If you should mess up, simply wipe /Library/Perl/ and re-install any extra modules and updates you need from CPAN. (That's the golden rule for Mac users, by the way: _never_ touch the /System tree -- almost everything else can be repaired.) >> 4. The vendor's (Apple's) updates don't have any effect on my work >> environment just as my work environment doesn't impinge upon the >> vendor's software. > > Has Apple ever pushed a perl update on you that did > not correspond to an OS version upgrade I've never had a problem with updates from Apple; except, as has been mentioned, that the Perl version tends to get a bit out of date and some new features may not be available until you by a new OS release. Just my €.02 ... Stefan _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
