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

Re: gnustep &c...

>>"Joel" == Joel Klecker <jk@espy.org> writes:

 Joel> We can't possibly have a /opt policy, since we aren't
 Joel> officially (i.e. as per the policy manual) using FHS yet.

	Firstly, following the FHSis a stated goal. We should not do
 anything now that woulf make adopting the FHS harder. 

	Secondly, we have had a long hiatus with regards to the actual
 policy documents. Just because the policy documents do not yet
 mention the FHS should not be taken very seriously. 

 Joel> I personally don't see why we can't use /opt for large
 Joel> subsystems such as GNUstep,
	Because /opt is reserveed for *add-on* application softwware. 

 Joel> /usr/lib/GNUstep is wrong,

	Umm, why? We may need to move the config files out (as we
 would for /opt, according to the FHS [/etc/opt]), and move the bin
 files out (leaving behind symlinks). This takes some work, initially,
 to package.

	But why is it wrong?

 Joel> /usr/GNUstep is wrong, /opt/GNUstep is really the only place
 Joel> GNUstep can be put both without stepping on the OPENstep
 Joel> standards, the FHS, or both.

	Sorry, the latter breaks the FHS.


Filesystem Hierarchy Standard                           October 26, 1997
3.8  /opt : Add-on application software packages

/opt -- Add-on application software packages
+-<package> Static package objects

/opt is reserved for the installation of add-on application software

A package to be installed in /opt shall locate its static files in a
separate /opt/<package> directory tree, where <package> is a name that
describes the software package.

Programs to be invoked by users shall be located in the directory
/opt/<package>/bin. If the package includes UNIX manual pages, they
shall be located in /opt/<package>/man and the same substructure as
/usr/share/man shall be used.

The directories /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib,
and /opt/man are reserved for local system administrator use.  Packages
may provide "front-end" files intended to be placed in (by linking or
copying) these reserved directories by the local system administrator,
but shall function normally in the absence of these reserved

Package files that are variable (change in normal operation) should be
installed in /var/opt.  See the section on /var/opt for more

Host-specific configuration files should be installed in /etc/opt.  See
the section on /etc for more information.

No other package files should exist outside the /opt, /var/opt, and
/etc/opt hierarchies except for those package files that must reside in
specific locations within the filesystem tree in order to function
properly.  For example, device lock files must be placed in /var/lock
and devices must be located in /dev.


The use of /opt for add-on software is a well-established practice in
the UNIX community.  The System V Application Binary Interface [AT&T
1990], based on the System V Interface Definition (Third Edition),
provides for an /opt structure very similar to the one defined here.

The Intel Binary Compatibility Standard v. 2 (iBCS2) also provides a
similar structure for /opt.

Generally, all data required to support a package on a system should be
present within /opt/<package>, including files intended to be copied
into /etc/opt/<package> and /var/opt/<package> as well as reserved
directories in /opt.


 Q: How does the Polish Constitution differ from the American? A:
 Under the Polish Constitution citizens are guaranteed freedom of
 speech, but under the United States constitution they are guaranteed
 freedom after speech. being told in Poland, 1987
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E

Reply to: