At 6:29 PM -0500 5/9/02, Jordan DeLong wrote: > > Symlink or redirector, but please not this. :-) > >Shouldn't ports *not* touch anything outside of ${PREFIX}? >I, for one, can't stand when ports do that >(except /etc/shells -- that's different).
I agree. That's why a redirector makes more sense, because the redirector can be part of the base-system, and the port can be installed in /usr/local. >Seems that neither symlink nor redirector is neccesary; >portable perl shebangs use #!/usr/bin/env perl to search >$PATH for it, and if the local sysadmin wants they can >make a symlink. Many many perl scripts already exist which do not do this. Yes, we now know that it would be more portable to write a script that way, but that doesn't magically change all the scripts which are already written and which are very used to assuming that perl is at /usr/bin/perl. Also, the /usr/bin/env approach means that scripts are now subject to the setting of $PATH, and that is not necessarily a good thing. Remember that the person running the script is not necessarily the person who wrote it, and is not necessarily aware that it even is a perl script, or that PATH is important when running that script. (PATH would not be important for a script which is using /usr/bin/perl) -- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message