From: brtmac@maverick.ksu.ksu.edu (Brett McCoy) Subject: Re: Linux-Activists Digest #20 Date: 28 Jan 1992 16:53:26
>Another approach is to setup areas such as
/usr/PACKAGE/bin
>along with its associated
/usr/PACKAGE/lib
/usr/PACKAGE/man
>etc etc.
>This makes for easier movement of toolsets when you are migrating from one
>OS version to another.
We've been fighting this battle on our Sun's here and still haven't come
up with any good concrete ideas except *don't touch the stuff that comes
with the system*. Anything installed should be put in /usr/local and the
standard /usr left alone. But, with linux, everything is installed because
nothing comes with the system so you wind up with an empty /usr. :)
Anyway, the /usr/PACKAGE/* idea doesn't work real well because you then
wind up with either huge long paths that no one ever gets set right or
zillions of symbolic links from /usr/local/* to /usr/PACKAGE/* that never
get updated when things change.
If anyone can come up with a good scheme I'd really like to hear it because
it would definitely make my life easier.