🚀 go-pugleaf

In article <1992Aug28.180137.22861@ra.msstate.edu> fwp@CC.MsState.Edu (Frank Peters) writes:
>In article <1992Aug28.155801.14501@sei.cmu.edu> kochmar@sei.cmu.edu (John Kochmar) says:
>: In article <1992Aug28.145234.17625@news.eng.convex.com>, Tom Christiansen <tchrist@convex.COM> writes:
>: |> In the particular case of perl, it really does make things *much*
>: |> easier if there is an agreed-upon, standard location.  The 
>: OK, I'll bite: why is it that it is much easier if perl is in an agreed
>: upon place like /usr/bin?
>Because perl is a scripting language.  That means it wants to have a #!
>line at the beginning with the path name to an executable.  Distributing
>code in this situation can be an annoyance unless you can arrange to
>have the path to perl be the same on different systems.
>
>I'm not sure, though, that I would characterize this as "*much*
>easer".  It isn't that hard to edit a file or sed a collection of
>files.

Especially since the Camel book (the standard Perl reference) contains
a nice little Perl program to fix all the #! lines of scripts for your
system.

I don't put _anything_ in /usr anymore, not even symbolic links.  I don't
even mount "local" on "/usr"... it goes on "/local".  And my "/local" is
beginning to look more and more like a "/usr" partition all of it's own.
Someday not too long in the future I'll dump the vendors's /usr completely
and _then_ I'll mount my local partition on /usr.  *grin*.
--
Jurgen Botz                  |   Internet: JBotz@mtholyoke.edu
Academic Systems Consultant  |     Bitnet: JBotz@mhc.bitnet
Mount Holyoke College        |      Voice: (US) 413-538-2375 (daytime)
South Hadley, MA, USA        | Snail Mail: J. Botz, 01075-0629