Jesse Keating wrote:
On Mon, 04 Feb 2008 23:42:05 -0800
Andrew Farris <lordmorgul@xxxxxxxxx> wrote:
Perhaps the only good solution to that is to have two groupremoves...
one that removes the *unique group members* and one that removes the
*entire group*. I cannot think of any reason there would be the need
for additional interpretations of groupremove.
yum groupremove --all or --force
groupremove by default removes entities that are only found in said
group and not in other groups or required by things in other groups.
Least surprise. --all or --force will remove all entities in said
group regardless of overlapping members.
I think that would be a good change to make, and would certainly be a better
safeguard for users only working in an interface to yum who might not understand
groups overlap at all.
A new user would expect that when they install a group, whatever got added will
be what goes away when they remove the group. The group install and group
remove are reasonably expected to be inverses. An additional 'yeah I want to
nuke it' flag would be great for this.
--
Andrew Farris <lordmorgul@xxxxxxxxx> www.lordmorgul.net
gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
