From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs
Date: Thu, 20 Sep 2007 17:54:27 -0400 [thread overview]
Message-ID: <20070920215427.GL30221@thunk.org> (raw)
In-Reply-To: <46F2D678.4060203@redhat.com>
On Thu, Sep 20, 2007 at 03:22:16PM -0500, Eric Sandeen wrote:
> I'd do this, my rpm-fu is still reasonably strong, though - I'm curious,
> is there a compelling reason to split out just libcom-err? what about
> libuuid? libblkid? e2fsprogs is a bit of a grab bag of things. What's
> the rationale for the split?
Nope, there isn't much rationale unless we also split out fsck, so
that people who don't want to use any ext 2/3/4 filesystems don't need
to install programs like e2fsck, mke2fs, libext2fs.so, etc.
The main reason why Debian did was more out of code wanking reasons
than anything else, as far as I know....
- Ted
next prev parent reply other threads:[~2007-09-20 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 6:14 [PATCH] obsolete libcom-err for SuSE e2fsprogs Andreas Dilger
2007-09-20 1:41 ` Eric Sandeen
2007-09-20 5:09 ` Andreas Dilger
2007-09-20 20:22 ` Eric Sandeen
2007-09-20 20:42 ` Andreas Dilger
2007-09-20 21:54 ` Theodore Tso [this message]
2007-09-24 9:25 ` Karel Zak
[not found] ` <20070924092539.GC2819-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-24 12:40 ` Theodore Tso
[not found] ` <20070924124035.GA4209-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-09-24 13:16 ` Eric Sandeen
2007-09-25 9:14 ` Karel Zak
2007-09-25 10:11 ` Kay Sievers
2007-09-25 12:34 ` Karel Zak
2007-09-25 15:20 ` Theodore Tso
[not found] ` <20070925123454.GE2806-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-25 20:25 ` Kay Sievers
2007-09-25 20:57 ` Karel Zak
2007-09-25 21:35 ` Christoph Hellwig
2007-09-25 9:27 ` Matthias Koenig
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=20070920215427.GL30221@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).