In a message dated Tue, 28 Aug 2007, Marek Stepanek writes:
> First I installed a new Perl 5.8.8 in /usr/local/ - Apple's OSX is
> up-to-date and Xcode installed!
>
> First something, where I am not sure about: I made
>
> % mv /usr/bin/perl /usr/bin/perl_out
> % ln /usr/local/bin/perl5.8.8 /usr/bin/perl
>
> Is this right?
"Right" in what sense? This will have the effect of "/usr/bin/perl", or
just "perl" in most PATHs, using your install rather than the Apple
install, if that's what you mean by "right".
However, you now have Apple code running against a Perl it wasn't tested
with, and you are keeping around all of a Perl version that is no longer
usable, just wasting disk space (since, to my knowledge, no programs start
with #!/usr/bin/perl_out).
I personally would undo your last two steps, and just write your programs
to use #!/usr/local/bin/perl, and adjust your PATH so that /usr/local/bin
comes before /usr/bin. That way, code written for Macs that expects
#!/usr/bin/perl to be the Apple-supplied Perl will continue to work as
expected.
Trey
|
