linux-ext4 - Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <n7xmyvbccxp.fsf@sor.suse.de>
Date:	Tue, 25 Sep 2007 11:27:30 +0200
From:	Matthias Koenig <mkoenig@...e.de>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Andreas Dilger <adilger@...sterfs.com>,
	"Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

Eric Sandeen <sandeen@...hat.com> writes:

> 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?

The Suse split out of library packages has been enforced by our new library
packaging policy[1]. I think debian has a similar policy [2].
In openSUSE the splitted out library packages are
libblkid1
libcom_err2
libext2fs2
libuuid1
with the corresponding development packages named with the -devel
postfix but without the soname version appendix. There is currently also
a dummy e2fsprogs-devel package for backwards compatibility.

I am not sure how other RPM based distributions will handle this and
if it is worth the effort to keep track of all this in one specfile.
If needed I could take care for the Suse specific stuff.

Matthias 

[1] http://en.opensuse.org/Shared_Library_Packaging_Policy
[2] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
-
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