From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs
Date: Thu, 20 Sep 2007 15:22:16 -0500 [thread overview]
Message-ID: <46F2D678.4060203@redhat.com> (raw)
In-Reply-To: <20070920050923.GX32520@schatzie.adilger.int>
Andreas Dilger wrote:
> On Sep 19, 2007 20:41 -0500, Eric Sandeen wrote:
>> Andreas Dilger wrote:
>>> It isn't possible to build an e2fsprogs via "make rpm" on SuSE and have it
>>> install cleanly, because they split out some of the libraries into separate
>>> packages.
>>>
>>> We've got the current patch to the .spec file, but I'm open to discussion
>>> if it is more desirable to change the .spec to continue to build separate
>>> RPMs (though that is more of a distribution hassle and might need major
>>> changes in the .spec file).
>> FWIW, I also have an RFE assigned to me for RHEL/Fedora to split up our
>> e2fsprogs packages for libcom_err and libuuid... since many
>> non-filesystem things now require them. So, this is sort of going in
>> the opposite direction. :)
>>
>> Any idea how many distros already split it out?
>
> I know Debian-based distros have done this for ages...
>
> I'd also welcome someone with rpm-fu split it into separate packages.
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?
-Eric
next prev parent reply other threads:[~2007-09-20 20:22 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 [this message]
2007-09-20 20:42 ` Andreas Dilger
2007-09-20 21:54 ` Theodore Tso
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=46F2D678.4060203@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).