On Thu, Aug 10, 2006 at 01:32:21AM +0200, Christian Iseli wrote: > For the moment, I used those rules to filter the packages: > ignore a package named P-xxx if a package named P is in Core or Extras > ignore packages where the string "plugin" appears in their name > ignore packages with names starting with: > lib > compat- > font(s)- > gtk- > kmod- > xfce4- > ignore packages with names ending with: > -devel > lib(s0-9) > -python > -perl > -server(s) > -client(s) > -tool(s) > -contrib(s) > -doc(s) > -(x)emacs > -util(s) > -font(s) Wouldn't it be better to have some kind of (fake) full installation of all comps.xml content + dependencies (something like the old rpmdb package using --justdb like semantics) and filter out the packages that were installed as dependencies - or even easier all packages that were installed that way? The remaining packages are exact those that are inaccessible from comps.xml and these are the ones we'd like to deal with. For example ignoring all -devel packages in comps.xml is bad, why shouldn't a user be able to develop on his system? The FC comps does include development groups for instance. If yum has --justdb support it would be very easy, if not, maybe it's trivial for Seth or someone else to add it to yum, if it makes sense. -- Axel.Thimm at ATrpms.net
Attachment:
pgpMx7opfRnhU.pgp
Description: PGP signature
-- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
