public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke Ravitch <luke@dslextreme.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why the FHS can't be followed
Date: Tue, 2 Jul 2002 13:06:08 -0700	[thread overview]
Message-ID: <20020702200608.GB5646@ogremage.dslxtreme.com> (raw)
In-Reply-To: <200207021410.00311.jsmith@kcco.com>

On 2002-07-02 12:09, Jean-Michel Smith <jsmith@kcco.com> wrote:
> However, I'm a little confused why (or how) it was decided that /opt
> would be an inappropriate place to have put this.  In other words,
> why is /usr/kde/3 and /usr/kde/2 better than /opt/kde/3 and
> /opt/kde/2?  I'm not criticizing (I have no real opinion on FHS
> compliance, or lack thereof, at all), I'm just wondering what the
> rationale is for not wanting to put things like this in /opt.

My feeling is that nothing in the /usr tree should depend on anything
in /opt.  Things in /opt are meant to be self-contained.  If we put
Gnome and KDE in /opt, where do we put apps that optionally depend on
them?  E.g, XMMS isn't really a gnome app (and so shouldn't be under
/opt/gnome) but can have Gnome dependencies (for the applet).

Gnome and KDE are most like X.  X has its own directory in /usr.  It
is part of the system.  As such, it's not such a big deal if programs
that depend on X live outside the X tree.  Of course, the FHS
considers /usr/X11 an unfortunate goof that, sadly, needs to be kept
around because of the tremendous inertia behind it.

Though I'm generally a big supporter, I think the FHS might be wrong
on this one.  Gnome and KDE should go under /usr/gnome and /usr/kde.
I do agree that adding an immediate subdirectory of /usr is not
something that should be taken lightly.  However, Gnome and KDE are
significantly entrenched as part of Gentoo that they might warrant an
X-like exception.

Another idea (likely a better one) is to put Gnome and KDE in their
own directories under /usr/X11R6.  FreeBSD has GTK and Gnome apps (I
don't know what they do with KDE, I imagine it's similar) in the X11
tree.  That's always seemed right to me.  But they put them in there
like we dump Gnome into /usr, so there isn't the advantage of separate
trees for separate versions.  I think /usr/X11R6/gnome and
/usr/X11R6/kde trees could really work out well.  And I don't think
the FHS regulates the contents of the X11 tree, so we'd keep them
happy as well.

My $0.02.

-- 
Luke


  reply	other threads:[~2002-07-02 20:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 23:37 [gentoo-dev] gentoo & fhs Collins
2002-07-01 16:06 ` Miguel S. Filipe
2002-07-02  0:50 ` Spider
     [not found]   ` <20020701190627.28c32c2e.erichey2@attbi.com>
2002-07-02  1:47     ` Spider
2002-07-02  2:38       ` Collins
2002-07-02 12:02         ` Alexander Gretencord
2002-07-02 15:12           ` Karl Trygve Kalleberg
2002-07-02 12:53         ` [gentoo-user] " Grant Goodyear
2001-12-08 13:21           ` Maciek Borowka
2002-07-02 15:55           ` Jean-Michel Smith
2002-07-02 17:00           ` Bart Verwilst
2002-07-02 18:41         ` [gentoo-dev] Why the FHS can't be followed Dan Armak
2002-07-02 19:10           ` Jean-Michel Smith
2002-07-02 20:06             ` Luke Ravitch [this message]
2002-07-02 22:00               ` Jean-Michel Smith
2002-07-03  1:54                 ` Luke Ravitch
2002-07-03  3:08                   ` Fuper
2002-07-05 16:33                     ` [gentoo-dev] Stow (Was: Why the FHS can't be followed) Wout Mertens
2002-07-05 16:59                       ` Brian Webb
2002-07-05 22:39                         ` Fuper
2002-07-05 17:14                       ` Alexander Gretencord
2002-07-02 22:18               ` [gentoo-dev] Why the FHS can't be followed Fuper
2002-07-03  2:05                 ` Luke Ravitch
2002-07-03  1:10               ` Peter Ruskin
2002-07-02 20:55           ` Terje Kvernes
2002-07-02 15:09 ` [gentoo-dev] gentoo & fhs Karl Trygve Kalleberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020702200608.GB5646@ogremage.dslxtreme.com \
    --to=luke@dslextreme.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox