This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: A modest proposal #1: /opt
- From: "Max Bowsher" <maxb at ukf dot net>
- To: "Charles Wilson" <cygwin at cwilson dot fastmail dot fm>,<cygwin-apps at cygwin dot com>
- Date: Sat, 19 Apr 2003 09:17:27 +0100
- Subject: Re: A modest proposal #1: /opt
- References: <20030418233522.8955D51A8B@smtp.us2.messagingengine.com>
Charles Wilson wrote:
> In certain ***RARE*** cases, I believe that a /opt/<package>/ heirarchy
> -- with the associated /etc/opt/ and /var/opt/ areas -- is a useful and
> necessary expansion of the official cygwin packaging standard. This
> would be an acceptable location for *official* cygwin mirror-distributed
> packages, but only in rare cases and after per-package justification on
> this list. For more information on the /opt heirarchy, see
>
> http://www.pathname.com/fhs/2.2/fhs-3.12.html
...
> Oh, and one other thing: the /opt tree should not (according the the FHS)
> be solely reserved for distributor use (e.g. official cygwin packages).
> Since every package is well-separated into it's own /opt/<package>/ tree,
> Bob can provide "Bob's ToolSet" in /opt/bobtool/ if he wants to --
> without censure from this list, even if bobtool is not an official cygwin
> package.
Because of this non-reserved nature of /opt, what about using
/usr/<packagename> - after all, we already have /usr/autotool, and kerberos
often goes into /usr/kerberos, doesn't it?
This leaves the contested /opt heirarchy safely untouched.
Max.