Bug 80276 - RFE: Finer-grained package selection during update
RFE: Finer-grained package selection during update
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-12-23 16:52 EST by H. Peter Anvin
Modified: 2007-04-18 12:49 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-12 12:42:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description H. Peter Anvin 2002-12-23 16:52:57 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020828

Description of problem:
When choosing "select packages to update" during a system update, it is unclear
what the checkbox actually does.  It would be a lot nicer if one could choose
between three alternatives: UPDATE, LEAVE, and DELETE.  (Say, for example, green
checkmark, blue dash, and red trashcan.)  Being able to delete a package would
be nice especially when space is tight.

If the currently installed version is the same as the current version, the
UPDATE alternative should either be unavailable or indicated as redundant,
perhaps by putting the green checkmark and blue dash within parenthesis.  This
is important, since a missing checkmark right now doesn't explain if it's
missing because the package is already up to date.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Upgrade an existing system
2. Choose customize packages


Additional info:
Comment 1 Bill Nottingham 2002-12-24 16:18:51 EST
As for package removal, I'm not sure that package removal is bound in the
installer context.
Comment 2 Michael Fulbright 2002-12-27 10:46:15 EST
We will consider this request for a future release.

Note You need to log in before you can comment on or make changes to this bug.