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: <20070920204238.GK32520@schatzie.adilger.int>
Date:	Thu, 20 Sep 2007 14:42:38 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

On Sep 20, 2007  15:22 -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?

Well, I think its just "e2fsprogs needs (and largely developed) these things
and Ted doesn't want external package dependencies".  There isn't a strong
reason to have them in a single package, especially as you say there are
more external packages that begin to depend on them, and e2fsprogs
(the libext2fs, e2fsck, etc. part) shouldn't necessarily be a "required"
package.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
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