/opt verus /usr/local

/opt verus /usr/local

Post by Blake LeBaro » Thu, 18 May 2000 04:00:00



I'm a new linux user, and I'm confused on one aspect of it.  Where is
the the appropriate place to put installed software packages?  I see
some want to go to /opt, and others prefer /usr/local.  What is the
current standard for this?

Blake LeBaron

 
 
 

/opt verus /usr/local

Post by Bob Tenne » Thu, 18 May 2000 04:00:00


 >I'm a new linux user, and I'm confused on one aspect of it.  Where is
 >the the appropriate place to put installed software packages?  I see
 >some want to go to /opt, and others prefer /usr/local.  What is the
 >current standard for this?
 >
I suggest using /opt for packages that insist on being kept together
under a directory.  This is usually the case for commercial packages
such as WordPerfect.  Use /usr/local for packages that distribute
themselves into standard sub-directories such as bin, lib, man, etc, src,
include, and so on.  But "whole" packages can go under /usr/local as well.

Bob T.

 
 
 

/opt verus /usr/local

Post by Markus Kossman » Thu, 18 May 2000 04:00:00



> I'm a new linux user, and I'm confused on one aspect of it.  Where is
> the the appropriate place to put installed software packages?  I see
> some want to go to /opt, and others prefer /usr/local.  What is the
> current standard for this?

Read the Filesystem Hierarchy Standard ( http://www.pathname.com/fhs/ )

--
Markus Kossmann                                    

 
 
 

/opt verus /usr/local

Post by Praedor Tempu » Fri, 19 May 2000 04:00:00





> >  >I'm a new linux user, and I'm confused on one aspect of it.  Where is
> >  >the the appropriate place to put installed software packages?  I see
> >  >some want to go to /opt, and others prefer /usr/local.  What is the
> >  >current standard for this?

> > I suggest using /opt for packages that insist on being kept together
> > under a directory.  This is usually the case for commercial packages
> > such as WordPerfect.  Use /usr/local for packages that distribute
> > themselves into standard sub-directories such as bin, lib, man, etc, src,
> > include, and so on.  But "whole" packages can go under /usr/local as well.

> Another thing to consider is the size of the package. Things that're
> huge, like KDE, Gnome, WP, etc also tend to go into /opt.

Ugh.  No thanks.  It is confusing and pointless to have redundant
directories.  /opt and /usr/local fall into the redundant catagory.
I don't care if it goes to /opt or /usr/local but it would be real nice
if a generic standard were decided for linux (all distros).  All things
that tend to be tied closely to linux (X, wms, glibc, gcc, etc) are all
under /usr.  All things that can vary from linux to linux on a more
personalized level (povray, blender, xephem, wordprocessors or office
suites) goes under /usr/local (or /opt...one or the other - or /home for
individuals who alone wish to use something).  It shouldn't matter how
large the package is, you simply make the mountpoint or partition large
enough to accomodate.  It doesn't matter if a package wants to be all
together since being all together can be accomplished in or out of /opt.
It can all be kept together in its own directory under /usr/local every
bit as easily as it can under /opt.  

Basically, they are redundant and confusing.  I tend to not permit /opt
to exist on my systems.  I relocate everything that wants to go there
into /usr/local.

praedor

 
 
 

/opt verus /usr/local

Post by JEDIDI » Fri, 19 May 2000 04:00:00






>> >  >I'm a new linux user, and I'm confused on one aspect of it.  Where is
>> >  >the the appropriate place to put installed software packages?  I see
>> >  >some want to go to /opt, and others prefer /usr/local.  What is the
>> >  >current standard for this?

>> > I suggest using /opt for packages that insist on being kept together
>> > under a directory.  This is usually the case for commercial packages
>> > such as WordPerfect.  Use /usr/local for packages that distribute
>> > themselves into standard sub-directories such as bin, lib, man, etc, src,
>> > include, and so on.  But "whole" packages can go under /usr/local as well.

>> Another thing to consider is the size of the package. Things that're
>> huge, like KDE, Gnome, WP, etc also tend to go into /opt.

>Ugh.  No thanks.  It is confusing and pointless to have redundant
>directories.  /opt and /usr/local fall into the redundant catagory.

        Actually in practice they seem to have completely different
        structure. /usr/local is essentially of /usr, while /opt is
        more of a /Program Files sort of organization with ENTIRE
        applications being limited to a single directory tree instead
        of spread out across an entire set of subdirectories.

        rm -r /opt/kde is actually a quite nice thing to be able to do.

Quote:>I don't care if it goes to /opt or /usr/local but it would be real nice
>if a generic standard were decided for linux (all distros).  All things

        There are 'generic' standards for Unix IN GENERAL. Linux reflects
        this. The minor differences aren't the sort that should be relevant.
        No shell should need to care where exactly a particular binary or
        library is.

[deletia]

        Nope, /opt is meant for a different sort of structure than /usr/local.

--

    In what language does 'open' mean 'execute the evil contents of'    |||
    a document?      --Les Mikesell                                    / | \

                                      Need sane PPP docs? Try penguin.lvcm.com.

 
 
 

/opt verus /usr/local

Post by Harlan Grov » Fri, 19 May 2000 04:00:00



<snip>

Quote:>Another thing to consider is the size of the package.
>Things that're huge, like KDE, Gnome, WP, etc also tend to
>go into /opt.

Depends on distribution. Red Hat puts KDE and Gnome in /usr
rather than either /opt or /usr/local.

* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful

 
 
 

/opt verus /usr/local

Post by Harlan Grov » Fri, 19 May 2000 04:00:00






>>scribble:
>>>I suggest using /opt for packages that insist on being
>>>kept together under a directory.  This is usually the
>>>case for commercial packages such as WordPerfect.
>>>Use /usr/local for packages that distribute themselves
>>>into standard sub-directories such as bin, lib, man,
>>>etc, src, include, and so on.  But "whole" packages can
>>>go under /usr/local as well.

<snip>

Quote:> . . . It doesn't matter if a package wants to be all
>together since being all together can be accomplished in
>or out of /opt. It can all be kept together in its own
>directory under /usr/local every bit as easily as it can
>under /opt. Basically, they are redundant and confusing.
>I tend to not permit /opt to exist on my systems.  I
>relocate everything that wants to go there into /usr/local.

Looks like /opt is intended to be similar to Windows's
Program Files directory, which would make it a mystery why
relatively basic stuff like KDE or Gnome would be put
there. However, I can't figure out why /opt/bin is needed
as opposed to symlinks in /usr/local/bin.

I think the following case could be made for the presence
of both /usr/local and /opt. Commercial applications change
infrequently, and could be located on read-only media.
Indeed, if the software only needed to add directories and
files to /etc and individual users' HOME directories, then
there could be mount points under /opt for CDs containing
these packages.

Noncommercial software is more likely to use traditional
subdirectory hierarchy (bin, doc, lib, man, etc.), and it's
likely to change more frequently. There's more of an
argument for it to be located on read-write media to
accomodate such changes.

We could take this further. Why is there a /usr/games
directory? Shouldn't everything be under /usr/local/games?
If /opt is unnecessary, what's the point of /mnt since
mount points could be created under /tmp? However, I go the
other way. If /opt and /usr/local were for commercial and
noncommercial packages, respectively, /opt shouldn't be
copied from machine to machine but /usr/local could be,
and /opt and /usr/local could have different backup admin.

[Getting very esoteric, /opt/<package> could contain
multiple subdirectories for different architectures,
e.g., /opt/XYZ/i386, /opt/XYZ/PPC, /opt/XYZ/sparc
and /opt/XYZ/noarch, in which case a single /opt could be
shared across a network of heterogenous machines. On the
other hand, /usr/local is pretty clearly machine-specific.
But this goes back to whether /opt/bin makes sense.]

* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful

 
 
 

/opt verus /usr/local

Post by Paul Kimo » Fri, 19 May 2000 04:00:00



> Red Hat puts KDE and Gnome in /usr
> rather than either /opt or /usr/local.

If it's packaged by the distributor of the whole system, it should go in
/usr or somewhere similar.  /opt and /usr/local are for things that come
from other sources.

--

 
 
 

/opt verus /usr/local

Post by Tom Fawcet » Fri, 19 May 2000 04:00:00


Are you all unaware of the Filesystem Hierarchy Standard?
(http://www.pathname.com/fhs/2.0/fhs-toc.html)
Or are you disagreeing about what it says?

-Tom

 
 
 

/opt verus /usr/local

Post by Frank Ha » Sat, 20 May 2000 04:00:00




>> Red Hat puts KDE and Gnome in /usr
>> rather than either /opt or /usr/local.

>If it's packaged by the distributor of the whole system, it should go in
>/usr or somewhere similar.  /opt and /usr/local are for things that come
>from other sources.

One package that I will suggest to make this easier is the opt_depot
package.  You need to have perl installed.  Once setup, every software
package you install goes in its own separate directory.  I place all
of my add on software in the /opt/depot/ directory.

Once the package is installed, you would then run opt_depot and it
makes the links to your /usr/local/ directory.  This makes it easy to
delete packages, etc.  You also only need to have the /usr/local/bin
directory in your path.

There are several other programs that allow you to do the same thing.
The last time I looked at the opt_depot web page, it had links to
this software.

Try here for the software:

http://www.arlut.utexas.edu/csd/opt_depot

--
Frank Hahn

"Who cares if it doesn't do anything?  It was made with our new
Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..."

 
 
 

/opt verus /usr/local

Post by Thomas Zaj » Sat, 20 May 2000 04:00:00



Quote:> Are you all unaware of the Filesystem Hierarchy Standard?
> (http://www.pathname.com/fhs/2.0/fhs-toc.html)
> Or are you disagreeing about what it says?

Are you unaware that FHS-2.0 ist obsolete and has been superseded
by FHS-2.1? See <http://www.pathname.com/fhs/>.

;-)

SCNR,
Thomas
--
=-------------------------------------------------------------------------=

-  "It is not easy to cut through a human head with a hacksaw."  (M. C.)  -
=-------------------------------------------------------------------------=

 
 
 

/opt verus /usr/local

Post by Dave Bro » Sat, 20 May 2000 04:00:00




>> I suggest using /opt for packages that insist on being kept together
>> under a directory.  This is usually the case for commercial packages
>> such as WordPerfect.  Use /usr/local for packages that distribute
>> themselves into standard sub-directories such as bin, lib, man, etc, src,
>> include, and so on.  But "whole" packages can go under /usr/local as well.

>Another thing to consider is the size of the package. Things that're
>huge, like KDE, Gnome, WP, etc also tend to go into /opt.

Since I have 2 Linux partitions on each of my machines, Slackware and RedHat,
(Note 1), and share /home, /opt, and /var/spool/mail between them, I
use /opt for applications such as WP and Acrobat that are not part of either
distribution, but needed in both.  I can also network mount /opt to machines
that don't have such installed.  I use /usr/local for software that's
part of one distro but not part of the other, (and for look-see's at stuff
that I might want to try out).

There's just as big a discrepancy (FHS notwithstanding) to apps that
want to install in /usr/lib.  And occasionally /var/lib.  And where to
put source code that you download?  --/usr/local/src, /usr/src, etc.?

(Note 1: used Slackware for years, but have to support RH customers.
 Note also that to share /home and /var/spool/mail, you have to keep
 UIDs and GIDs in sync between the two.)

--
Dave Brown  Austin, TX

 
 
 

/opt verus /usr/local

Post by JEDIDI » Sat, 20 May 2000 04:00:00



Quote:

>Are you all unaware of the Filesystem Hierarchy Standard?
>(http://www.pathname.com/fhs/2.0/fhs-toc.html)
>Or are you disagreeing about what it says?

        What's to disagree with?

        That doc says that /usr/local is an iteration of /usr reserved for
        'local use' and /opt conforms to the /opt/<atomic package> format.

        This is not significantly different than how both have been used
        for 5+ years now on Linux and Solaris.

--

    In what language does 'open' mean 'execute the evil contents of'    |||
    a document?      --Les Mikesell                                    / | \

                                      Need sane PPP docs? Try penguin.lvcm.com.

 
 
 

/opt verus /usr/local

Post by Peter T. Breue » Sat, 20 May 2000 04:00:00


: Program Files directory, which would make it a mystery why
: relatively basic stuff like KDE or Gnome would be put
: there. However, I can't figure out why /opt/bin is needed

It isn't really. Yes I too put ...

: as opposed to symlinks in /usr/local/bin.

: I think the following case could be made for the presence
: of both /usr/local and /opt. Commercial applications change

You don't need a case. It's easy: /usr: the distro: /usr/local: you
/opt: A Third Party.

: We could take this further. Why is there a /usr/games
: directory? Shouldn't everything be under /usr/local/games?

No. Rogue/Hack are "official". No distro is complete without them.

Peter

 
 
 

/opt verus /usr/local

Post by Peter T. Breue » Sat, 20 May 2000 04:00:00


: Ugh.  No thanks.  It is confusing and pointless to have redundant
: directories.  /opt and /usr/local fall into the redundant catagory.

No they don't. /usr/local is for your additions. /opt is for (large)
third party additions.

: I don't care if it goes to /opt or /usr/local but it would be real nice
: if a generic standard were decided for linux (all distros).  All things

There is one. Try reading it. FSSTND.

: Basically, they are redundant and confusing.  I tend to not permit /opt
: to exist on my systems.  I relocate everything that wants to go there

I like /opt. Good idea. Now if they would just start up a
/usr/dist as well as /usr/local.

Peter

 
 
 

1. /usr/bin, /usr/local/bin, /sbin or /opt/bin, /var/opt/bin - I'm confused.

Hi all,

All these directories are for executable binary, right ?  How does one
decide which executable binary goes to which directory ?

/usr/bin : For what ?
/usr/local/bin:  for what ?
/sbin : ??
/opt/bin : ??
/var/opt/bin : ??

Is there any other /bin beside those above ?

Thanks

2. mmap & LARGEFILE

3. What is Sun's preferred directory: /usr/local/bin or /opt/local ?

4. Minimal X with Virge S3 & XF 3.1.2 or Metro X?

5. Should local software go in /opt or /opt/local?

6. Scary VM message with Linux 2.4.19-pre9-ac3

7. /usr/local and /opt

8. term-aware Mosaic-2.1?

9. /opt and /usr/local under Solaris...

10. Do I need /usr/local, /opt, /tmp and /var partitions?

11. /usr/local, /opt, and NFS

12. Newbie: Difference between /opt and /usr/local?

13. /opt vs /usr/local