Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'don't use CPAN for /usr/bin/perl' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
don't use CPAN for /usr/bin/perl
Authored by: mzs on Jul 20, '09 08:30:38AM
That's all great in theory but in practice it does not work:

http://www.macosxhints.com/article.php?story=20090219082024982

http://www.theregister.co.uk/2009/02/16/apple_update_perl_breakage/

There is blame to go around to all parties (like doing what you say is essentially impossible do to the way module paths work in perl) but the rule of thumb is that for the system installation of perl, only use the vendors packages for that (that goes for linux distros as well) and use another perl install for everything else. The main reason for this is all the perl scripts that are from your vendor which you do not want to break with a newer unexpectedly incompatible version of something or other.

[ Reply to This | # ]
don't use CPAN for /usr/bin/perl
Authored by: CarlRJ on Jul 21, '09 12:53:37AM
That's all great in theory but in practice it does not work ... There is blame to go around to all parties (like doing what you say is essentially impossible do to the way module paths work in perl)

Uh, look, are you sure you understand the definitions of the words "theory" and "practice"? I've been using Perl this way for the past half dozen years (on the Mac, that is -- I've been programming in Perl on various platforms since the early 90's) and it has been working just fine for me in practice. I'm not looking to have an argument, but please don't tell me that something I have been doing can't be done.



[ Reply to This | # ]