On Thu, 2007-01-18 at 20:05 -0500, seth vidal wrote: > On Thu, 2007-01-18 at 17:59 -0500, Fernando Nasser wrote: > > David Lutterkort wrote: > > > On Thu, 2007-01-18 at 09:11 -0500, Fernando Nasser wrote: > > >> seth vidal wrote: > > >>> why do you need a 'groupexclude' option? I guess I don't understand the > > >>> use case for it, yet. > > >>> > > >> For instance, to upgrade one's Fedora system without interfering with > > >> the Java stack there. > > > > > > What happens to your Java stack at that point ? Will it just stay > > > frozen ? > > > > > > > That is the idea, update your Fedora system except for the Java > > packages, which you can update selectively, from a different repo, from > > local RPMs etc. > > > > so you want --groupexclude to exclude from the update all packages in > that group? Not exclude the group from the list of available groups? This is starting to be OT for this list, but wouldn't it be better if users could just add groups into the existing mechanisms with a separate notation, similar to kickstart ? I.e., instead of a separate --groupexclude, allow --exclude=@java ? David -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
