From: Fuper <futurist@directvinternet.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why the FHS can't be followed
Date: 02 Jul 2002 22:08:02 -0500 [thread overview]
Message-ID: <1025665683.2980.120.camel@silver.perimeter> (raw)
In-Reply-To: <20020703015424.GB3221@ogremage.dslxtreme.com>
On Tue, 2002-07-02 at 20:54, Luke Ravitch wrote:
> I'd be okay with something like:
>
> /usr
> +--->X11R6
> +--->gnome
> | +--->1
> | +--->2
> +--->kde
> +--->2
> +--->3
> So I vote for one of the above to layouts. Picking the right one is a
> matter of decided which gives the best breadth/depth ratio.
I agree. The whole discussion seems to move toward that conclusion. I
also now agree that Gentoo is not FHS compatible because it defines
non-standard directories in /usr.
Now, as for Stow -- I beat you up for not loving Stow! I may find some
drawbacks in the future that are not apparent to me now but it seems to
me that the tiny Stow script makes it possible to install, upgrade, and
remove software packages without depending on a database to track all of
the files. For example, I can answer the following questions without
reference to an rpm or dpkg (or portage) database:
Q: Which files were installed by FramerD?
(A: All of the files in /usr/local/stow/framerd-2.3/
Q: How can I upgrade mit-scheme from version 7.7 to 7.7.1?
(A: cd /usr/local/stow; stow -D scheme-7.7; stow scheme-7.7.1
Q: Which binaries are used for accessing Wordnet?
(A: ls /usr/local/stow/wordnet-1.7/bin
or ls -l /usr/local/bin | grep wordnet
That last one works because every binary is symlinked into local/bin and
so ls -l gives a clear view of what package each binary belongs to; e.g.
wishwn -> ../stow/wordnet-1.7/bin/wishwn
wn -> ../stow/wordnet-1.7/bin/wn
wnb -> ../stow/wordnet-1.7/bin/wnb
next prev parent reply other threads:[~2002-07-03 3:08 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 [this message]
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=1025665683.2980.120.camel@silver.perimeter \
--to=futurist@directvinternet.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