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