From: Wout Mertens <wmertens@gentoo.org>
To: Fuper <futurist@directvinternet.com>
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Stow (Was: Why the FHS can't be followed)
Date: Fri, 5 Jul 2002 18:33:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.GSO.4.44.0207051816160.18993-100000@oaktree.cisco.com> (raw)
In-Reply-To: <1025665683.2980.120.camel@silver.perimeter>
Hey there,
On 2 Jul 2002, Fuper wrote:
> On Tue, 2002-07-02 at 20:54, Luke Ravitch wrote:
> 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:
[...]
I agree, stow is cool and at work we use it to maintain our 12GB
/usr/local tree that is exported over nfs to our workstations.
Some drawbacks, however:
- You have a slight speed loss because of the symlinking adding
extra lookups. Luckily, Linux has very good caching :)
- Some packages hate it when you symlink stuff; e.g. sudo needs its
sudoers file to be a regular file. Granted, this is a configuration file
and as such may not need to be symlinked in a general gentoo context, so
this could be solved by just creating a regular file in the
pkg_postinst.
- stow -R can grind your server to a screeching halt if you have many
files. I'm sure this is solveable by rewriting the code a little, and I
don't know if recent versions have trouble with it since we don't try it
anymore ;)
- You have a lot of symlinks in your /usr, which makes ls -l a bit less
attractive to look at. Of course, there's still ls -lL ;-)
I've been considering nagging to drobbins about changing Portage so that
merging actually means
'Copy package to /var/db/packages/<cat>/<pkg>/files/ and symlink everything'
and unmerging means 'remove the symlinks'. Portage would then need a
purge option to remove the package files altogether.
This would have the advantage that you can always revert to a certain
version of a package with certainty, since no files are removed from the
previous package. And you see where a file comes from really quickly by
looking at the symlink, which is very useful.
And actually, I think it would be possible to let portage optionally have
that feature, because the only thing it changes is where the files are
installed and what merge and unmerge do. All the rest would stay the
same. That way, people who want it can turn it on and the rest aren't
bothered.
Thoughts?
Wout.
next prev parent reply other threads:[~2002-07-05 16:34 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 ` Wout Mertens [this message]
2002-07-05 16:59 ` [gentoo-dev] Stow (Was: Why the FHS can't be followed) 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=Pine.GSO.4.44.0207051816160.18993-100000@oaktree.cisco.com \
--to=wmertens@gentoo.org \
--cc=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