On Wed, 2003-07-30 at 11:11, Michael K. Johnson wrote:
On Wed, Jul 30, 2003 at 09:30:43AM +0300, Panu Matilainen wrote:
> OTOH anaconda *does* fiddle around with package selections to some extent on
> upgrades: there's code for removing blacklisted stuff (linuxconf, no wonder :),
> installing rhn-applet if up2date-gnome was installed, making sure certain GNOME
> packages are installed etc. Whether rhgb should be automatically added on
> upgrade .. well, I dunno.
Basically, the default answer is "don't fiddle". It's only done in
cases where there's a very strong reason. An "update" has never had
the requirement of producing the same effect as an "install" in Red
Hat Linux -- besides the fact that it is practically impossible to
achieve in practice, it's not necessarily what people want. We aim
for "functional with packages updated" and not automagically pulling
in rhgb on upgrade is inline with that policy.
I'm not sure I'd agree with this - OK, I'd agree that hard-coding
fiddling in anaconda is evil - but I think making sure that rhgb
gets installed for an upgrade of a workstation install of RH 9
is very much in line with what we've tried to do in the past.
Sometimes this involves hard-coding things in anaconda, in other
cases we've added extra package dependencies just to make sure
that things get pulled in.
But the goal is certainly that if you take a workstation install,
upgrade it to a newer version, you get the main workstation
features of the newer version.