🚀 go-pugleaf

In article <1992Aug30.215306.12595@puma.ATL.GE.COM> rsnyder@atl.ge.com (Bob Snyder) writes:
>In article <1992Aug28.183918.22664@sei.cmu.edu> kochmar@sei.cmu.edu (John Kochmar) writes:
>
>>You've gotta be kidding, right?  You're not advocating that perl be
>>placed in /usr/bin so that scripts you pick up from who-knows-where
>>will run without modification, right?
>>
>>I got the same response from someone else in private mail.  Since I
>>don't make a habit of picking up a script and running it without
>>checking it over, I don't see changing the #! at the beginning to be
>>that big a deal.

>But when you have a multi-user environment, and new users coming in, they
>expect that programs will be in certain commonly known locations, like sh
>and perl.  I don't neccesarily like where it goes, but that is where most
>people expect to find it.

Umm... folks?  You do know about symbolic links, don't you?  You do know that
it's common practice to put site-specific material in a non-/usr paritition
and place symbolic links from the /usr filesystem (or from /bin) to them?
This solves both problems.  In addition, it makes it a whole lot easier to
install a new operating system from scratch on another machine, and customize
it by copying over all the site specific information.
--scott