🚀 go-pugleaf

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 
|> preferred strategy is to put a link in /usr/bin pointing to 
|> where it actually lives, which varies from machine to machine.
|> 
|> Of course, those lucky folks whose vendors already ship perl 
|> on the system in /usr/bin have no such concern. (Hm, I've been
|> thinking of putting it in /bin so it's mounted with root. :-)
|> ...

OK, I'll bite: why is it that it is much easier if perl is in an agreed
upon place like /usr/bin?

We use /usr/local for all tools that aren't part of the standard
distribution that the vendor sends us, and I've made all sorts of
software work cleanly while living in /usr/local (and, in almost all
cases, without the use of symbolic links in /usr/bin.)  This model
works really well for us, and most tools will work with this model
if the programmers weren't of the lazy sort who like to hardwire
paths into the binary.

John



-----------------------------------------------------------------------------
John Kochmar		 | Estimated amount of glucose used by an adult human
kochmar@sei.cmu.edu	 | brain each day, expressed in M&Ms: 250
SEI Computing Facilities |			-Harper's Index, October 1989