Bug 10930 - Thoughts about package management and updating in general.
Summary: Thoughts about package management and updating in general.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution   
(Show other bugs)
Version: 6.2
Hardware: All Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Keywords: FutureFeature
: 28013 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-04-19 22:33 UTC by Pekka Savola
Modified: 2007-04-18 16:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-28 22:33:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Pekka Savola 2000-04-19 22:33:27 UTC
Some thoughts on Redhat's package management and update procedures
follow. I didn't get any response about this on redhat-list -mailinglist,
so I thought this might be a better channel to introduce some ideas.

I have been administering Redhat boxes for over four years now.  Recently,
I have noticed more and more that there's still one important component

I'd very much like to be able to select RPM's I want to install / want to
get uninstalled by categories like in Redhat installer even without running
the installer (ie. with an RPM management util).  I believe some of
this (selecting/deselecting by Group defined in RPM, e.g.
Applications/Archiving) is done in current X utils (text interface
would be a huge plus), but still there are a couple of major functionality
features to be considered.

I'd like deselecting/selecting of RPM's by installer categories also (as
read from RedHat/base/comps) or similarly defined file.  This would be
a great help for people that realize later on that they'd really need a web
server, forgot to choose development packages in install, etc.  No need
for re-installations or manual playing with RPM's after that.

Also, along the same lines.. an extension of above. I'd very much if the
some parts of redhat installer was released as a normal userland
program.  You could do updates without booting and having to go through
your partitions and other cruft.  That'd be really neat; a little like with
FreeBSD /stand/sysinstall.  Also, creating a centralized summary (e.g.
unified diff, or anything but just mere filenames) of .rpmsave and
.rpmnew changes would be a nice addition here; e.g. compare with the
really powerful _script_ mergemaster from  FreeBSD -- Redhat could use
something like that.

Updaters like AutoRPM do some of the above, but they can't handle
situations where new packages appear / are renamed very well, not
considering the usual hassle with .rpmsave .rpmnew etc. configuration files
after such an exhaustive upgrade.

HTH :)

Comment 1 Michael Fulbright 2000-06-12 19:03:56 UTC
Filed for future feature release.

Comment 2 Michael Fulbright 2000-09-26 16:09:41 UTC

Comment 3 Michael Fulbright 2000-09-26 16:55:23 UTC

Comment 4 Michael Fulbright 2001-09-14 16:35:36 UTC
Assigning to distribution component.

Comment 5 Brent Fox 2002-06-05 01:35:12 UTC
I'm going to assign this to katzj, since it seems very similar to what he's
working on.

Comment 6 Brent Fox 2002-06-05 03:20:29 UTC
*** Bug 28013 has been marked as a duplicate of this bug. ***

Comment 7 Jeremy Katz 2003-07-28 22:33:38 UTC
redhat-config-packages basically does the really doable parts of this

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