You are not logged in.
Pages: 1
Hello,
is there a reason and a logic why some software are located into /opt while other aren't ?
I usually put into /opt the software I've downloaded and installed myself (like firefox, planeshift or xsteem) , and keep it into a separate partition so I can access it from several linux distributions.
opt seems to stand for "optional application software packages". On some other sources, it's reserved for "add-on application software packages" ( http://www.pathname.com/fhs/2.2/fhs-3.12.html )
For example, why Kde into /opt, and not Gnome? Why java, virtualbox, openoffice and qt, and not the flash plugin or freemind?
Offline
Mostly big self-contained things were put there. gnome has been already pulled out, kde4 and qt4 aren't there anymore either. There have been countless topics about /opt, just search the forum.
Offline
software you installed by yourself should go in /usr/local.
Offline
There have been countless topics about /opt, just search the forum.
opt is such a short word and commonly used there are 300 pages of topics related to this. I've tried to add other keywords but really nothing much relevant came.
/usr/local is ok for self compiled software, but I prefer to keep precompiled binaries software into /opt
Offline
/usr/local is ok for self compiled software, but I prefer to keep precompiled binaries software into /opt
IMHO that's exactly what /opt is for: software which was compiled by 3d parties.
/opt is C:\Program Files
Offline
Putting simple: /opt is for 3rd party stuff that may not follow the /usr directory layout (bin, etc, lib, share...).
For example, a hipotetical software package that installs itself in Linux way would place files into this layout:
/usr/bin/myapp
/usr/lib/myapp/libfoo.so
/usr/lib/myapp/libfoo.so.1
/usr/share/myapp/myfooicon.pngIf there's a 3rd party package that doesn't follow this layout, then it should be put under the /opt tree
/opt/myweirdapp/Exec/myappbin
/opt/myweirdapp/Libraries/myapplib.so
/opt/myweirdapp/Documentation/myapplmanual.pdfThere's /opt/bin and /opt/lib though, that are intended to be under your PATH, so users can call binaries without going inside the application tree for each application, which is, of course, non-standard (e.g., /opt/myweirapp/Exec/myappbin)
More info:
http://www.pathname.com/fhs/pub/fhs-2.3 … REPACKAGES
Offline
Beginners' Guide explanation:
/opt/ Packages that do not fit cleanly into the above GNU filesystem layout can be placed here. If a package's files cannot be cleanly placed into the above directories, then /opt shall be used. /opt shall therefore contain shareable data.
For example, the acrobat package has Browser, Reader, and Resource directories sitting at the same level as the bin directory. This doesn't fit into a normal GNU filesystem layout, so Arch places all the files in a subdirectory of /opt.
Offline
I also use it if the package conflicts with an already existing package.
-$: file /dev/zero
/dev/zero: symbolic link to '/dev/brain'
Offline
Traditionally, they put difficult or weird applications in /opt just because it was easier to package that way (it was self contained.) The packaging standards have changed, so new packages do not go in /opt.
Many large apps have moved to the standard hierarchy, but some stay in /opt because nobody has taken the time to port them. The specific apps you mention are either a) difficult to move to a standard hierarchy (oo.o, kde) or b) maintained by one of the devs who doesn't have much time for Arch lately (Java).
/opt is a system folder, its not really meant to have user-created packages in it. In general, only /etc, /usr/local, /usr/src, /boot, and /home should contain files that have been changed by the user or sysadmin. In practice, of course, this is not a rule and should always be broken.
Dusty
Offline
Thank you all for the complete explanations!
Offline
Pages: 1