Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux & Slackware versions

lark at (Lar Kaufman) writes:

>Red Hat, doesn't put things in /usr/local for example,
>because it doesn't think software controlled by RPM distribution should 
>be there.

Slackware has the same policy.  I agree with it, and I believe the
file system standard agrees.  A GNU package (for example) normally
install itself in /usr/local by default, on the assumption that users
are installing it because their distribution did not include it.  That
also enables a user to install a new distribution without disturbing
it.  When a distributor makes a program available, he is assuming
responsibility for administering it.  Therefore, it's appropriate for
him to put it in /usr/bin, etc which is in his area.  Thus, perl for
example was in /usr/local/bin in most systems for a while, but it's
now "moving" to /usr/bin now that it has been accepted, and
distributors have taken responsibility for administering it.

                       - Jim Van Zandt

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /