NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Hmmm (Score:1)
A f
Re:Hmmm (Score:2)
It's been a while since I last used Solaris, but I never have encountered the problems you describe. Unlike most of the Linux distros I've worked with, Sun comes a long way of insuring that its own Perl dependent utilities still work if you change the default installation of perl. The main idea being that /usr/bin/perl is a link to someplace else. All the OSses scripts use the path of where /usr/bin/perl links to, leaving the admin free to replace /usr/bin/perl. It won't break any of the OSses scripts.
That still constitutes installing your own perl, right? The issue of whether it's in /usr/bin or elsewhere is relatively minor, to me. It's smart of them to tie their scripts to a specific installation somewhere outside of the regular hierarchy (and that's what I recommend we do with our programs and our own installation).
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This
Parent