From: Peter Ruskin <aoyu93@dsl.pipex.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why the FHS can't be followed
Date: Wed, 3 Jul 2002 02:10:42 +0100 [thread overview]
Message-ID: <200207030210.42348.aoyu93@dsl.pipex.com> (raw)
In-Reply-To: <20020702200608.GB5646@ogremage.dslxtreme.com>
On Tuesday 02 Jul 2002 21:06, Luke Ravitch wrote:
> 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.
FHS says /usr should be read-only. Some people are already providing /usr
over network read-only. Just think about all of KDE's global
configuration files in /usr/share/config for RedHat and Mandrake;
/usr/kde/{2,3}/share/config here. Well perhaps global configs should be
served readonly, but on my system they seem to change quite often and
there's a mess of them (56 files and 3 directories).
My guess is it's probably unworkable. Now we're unlikely to convince KDE
developers to put these all in an /etc somewhere (my Mandrake box has 78
/etc subdirectories already) and I'm quite happy to have the
/usr/kde/{2,3,4} for now. However, thinking about the read-only
requirement, I'd rather see /opt/kde/{2,3,4}.
BTW, posting this from the 'drake box due to hard disk crash on the gentoo
one.
--
Mandrake Linux release 8.2 (Bluebird) for i586
AMD Athlon(tm) XP 1600+ 513MB Kernel: 2.4.18-6mdk-pnr-win4lin
KDE: 3.0.1 Qt: 3.0.4 up 5 hours 18 minutes.
~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
next prev parent reply other threads:[~2002-07-03 1:11 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
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 [this message]
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=200207030210.42348.aoyu93@dsl.pipex.com \
--to=aoyu93@dsl.pipex.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