Package categorization and distribution construction

[David Tardon]

On Thu, Jan 19, 2012 at 03:43:43PM +0000, Richard W.M. Jones wrote:
> On Thu, Jan 19, 2012 at 09:40:56AM -0500, Daniel J Walsh wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On 01/19/2012 08:54 AM, Bill Nottingham wrote:
> > > Peter Robinson (pbrobinson at gmail.com) said:
> > >> Great idea, I would also love to see a clear out of the packages
> > >> that aren't core/part of particular categories. MTAs in minimal
> > >> would be one that comes to mind but there's lots of other
> > >> examples.
> > > 
> > > Yeah, I'd like to clean this up. The sad thing is that even if I
> > > define the minimal group as:
> > > 
> > > kernel dracut util-linux systemd systemd-units initscripts yum 
> > > selinux-policy-targeted policycoreutils
> > > 
> > > it merely drops it from 524MB/186 packages to 503MB/152 packages. I
> > > could make it smaller by dropping yum/rpm and dependencies, but I
> > > can't in good conscience ship an *installation target* minimal
> > > install that doesn't allow you to get updates or add-in packages.
> > > 
> > > Bill
> > > 
> > > 
> > 
> > Any headscratchers in the list or rpms?  I just saw that
> > policycoreutils had a Require for bunzip2, which it does not need.
> 
> I wrote a little graphical tool called rpmdepsize (it's in Fedora)
> which may be useful.  Unfortunately it only works with a single
> package, eg:
> 
>   rpmdepsize kernel

There is also rpmreaper. It does not allow to show the size of a package
including all its dependencies (it would be a nice feature :-), but it
is really good for examining dependencies, reverse dependencies and
dependency cycles of installed packages.

D.