Mea Culpa Yes I forgot about the group* commands that would do what I wanted. Thanks <div>On 11/5/07, Jima <<a href="mailto:jima@beer.tclug.org">jima@beer.tclug.org</a>> wrote: <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Mon, 5 Nov 2007, Mark Bidewell wrote: > Last week I tried moving to updates-testing in order to test latest KDE on > F7. The resulting kernel update was mismatched with kernel-devel so I could > not install the nvidia drivers. My suggestion is this. Would it be > possible to segregate updates according to package type (similiar to the > SUSE buildservice) or even just along the lines of Desktop (KDE/GNOME/etc > and deps) and System( kernel etc.) so testing bleeding edge packages from > one package group won't break other system packages? Not to derail your idea, but is this necessarily anything that `yum --enablerepo=updates-testing --exclude=kernel\* upgrade` wouldn't fulfill? At this point my brain started muttering something about "hey, wouldn't a `yum groupupgrade` command be awesome?" Which led me to look at the yum man page...which fails me. It only has groupupdate. *sad panda* Seth, would `groupupgrade` be a simple add-on? Or just pointless? Not sure if obsoletes are important enough... So yeah, in summary, I'm guessing `yum --enablerepo=updates-testing groupupdate "KDE (K Desktop Environment)"` will do what you want. Jima -- fedora-devel-list mailing list <a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list">https://www.redhat.com/mailman/listinfo/fedora-devel-list </a> </blockquote></div>