This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: RFD: A modest proposal #1: /opt
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 22 May 2003 15:16:53 -0400
- Subject: Re: RFD: A modest proposal #1: /opt
- References: <20030418233522.8955D51A8B@smtp.us2.messagingengine.com> <20030522034138.84D4E611E5@smtp.us2.messagingengine.com>
- Reply-to: cygwin-apps at cygwin dot com
On Wed, May 21, 2003 at 11:41:38PM -0400, Charles Wilson wrote:
>This conversation died out without a conclusion last month. If nobody
>else cares very much, but I think this idea is
>peachy-with-a-side-of-keen, does that mean I win? <g>
>
>Seriously, may we extend the 'official cygwin file system standard' to
>include an FHS-like /opt tree, for RARE use (e.g. only when the
>cygwin-apps community, during ITP discussion or package-review phase,
>arrives at a consensus that package FOO will be allowed to live in /opt)?
>
>IMO, the only current candidates for "/opt" treatment -- if we choose to
>allow it -- are the ast-open toolset, and the kerberos toolset, which
>each provide alternate implementations of existing tools in other
>packages. (I think the emerging symlink-based solution w.r.t. to pdksh
>and ast-ksh is appropriate; I don't think ast-ksh should be an /opt
>package. But ast-open should be.)
I really don't care if we decided to include /opt, fwiw. I don't have
strong feelings either way.
cg ever helpful f