[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Sep 2007 15:22:16 -0500
From: Eric Sandeen <sandeen@...hat.com>
To: Andreas Dilger <adilger@...sterfs.com>
CC: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs
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
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists