From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: Collins <erichey2@attbi.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo & fhs
Date: Tue, 2 Jul 2002 17:09:56 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.96.1020702170807.25281C-100000@pluto.prosalg.no> (raw)
In-Reply-To: <20020701173735.5d1093ae.erichey2@attbi.com>
On Mon, 1 Jul 2002, Collins wrote:
> gnome and kde are in the /usr hierarchy instead of the /opt hierarchy
> "where god intended them to be."
They lived in /opt before, but then that was suddenly very uncool and they
got moved to /usr. The binary packages were mostly allowed to say in
/opt.
It'd be nice to recruit an FHS zealot to handle all these pesky
path-details for us.
Karl T
prev parent reply other threads:[~2002-07-02 15: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
2002-07-02 20:55 ` Terje Kvernes
2002-07-02 15:09 ` Karl Trygve Kalleberg [this message]
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=Pine.LNX.3.96.1020702170807.25281C-100000@pluto.prosalg.no \
--to=karltk@prosalg.no \
--cc=erichey2@attbi.com \
--cc=gentoo-dev@gentoo.org \
--cc=karltk@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