Re: [gentoo-dev] Why the FHS can't be followed

[Fuper <futurist@directvinternet.com>]

The FHS _has_ been followed by Gentoo.

The use of /opt is optional.  The Standard places limitations on the use
of /opt and gives an historic rationale for it, but does not require
that anything be installed in /opt.

I would suggest that everyone actually read the FHS at
<http://www.pathname.com/fhs/>

BTW the restrictions are that any package installed in /opt must reside
entirely within it's own subdirectory /opt/<package> and that no package
may modify or delete software installed in /opt by the local system
administrator. Only the local administrator may install files into the
directories: /opt/bin /opt/include /opt/lib /opt/man /opt/info

Especially read the Rationale for /opt --- it was an AT&T System V
invention and is to hold "Add-on Software Packages" that are not a part
of the "System Software".  That made sense for System V for which
"System Software" had a definition.  There is much less clear
distinctions between "system" and "add-on" in a Linux system.  There is
no distinction between "system" and "add-on" in the Gentoo
meta-distribution.  In a meta-distribution it's all under local
administrator control.  

/opt is optional

BTW I prefer to place binary-only packages such as Acroread in /opt and
otherwise to keep /opt as small as possible.  I don't put any local
software in /opt and don't recommend that you do either.  /usr/local is
more traditional and if you like to keep apps contained within their own
package directories then use GNU Stow and install each package as
/usr/local/stow/<package>.  See
<http://www.gnu.org/software/stow/stow.html>

p.s. I passed the LPIC Level 1 exams!  They are tough.