On Tue, May 12, 2009 at 08:52:01AM -0500, Eric Sandeen wrote: > Richard W.M. Jones wrote: > > [I posted this before, but no one replied, so sending again to > > fedora-devel-list] > > > > https://bugzilla.redhat.com/show_bug.cgi?id=225406#c7 > > > > I would like to propose that e2fsprogs generate four subpackages for > > the independent libraries that it contains. These four libraries are > > used by other packages that don't need the whole of e2fsprogs-devel > > (eg. krb5_workstation uses libss, qpid uses libuuid, and many programs > > use libcom_err). > > I'm generally open to the suggestion, but last time I had this concern... > > > The next problem I see is that by putting things like blkid, uuidgen, > > compile_et, mk_cmds into the lib$FOO packages, they are now no longer > > multilib-safe; the binaries will collide. > > is this going to be a subpackage-explosion? for example: > > uuid.rpm (with the binary tool(s)) > uuid-libs.rpm > uuid-devel.rpm > > and so on for each of the above binary+libs? IMHO, having separate sub-packages for each of the command line tools is overkill. Just put the libraries in -libs & -devel, but keep all the binaries in e2fsprogs. This would avoid any multilib issues with binaries, and keep the number of sub-packages sane. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
