On Mon, 2003-03-24 at 13:07, Adam Williamson wrote: > > > Secondly, urpmi is still not quite good enough for doing a > > > between-versions upgrade entirely automatically, because of the problem > > > of adding new packages. It installed several config files which expected > > > the Galaxy theme packages, but of course it didn't install these, I had > > > to do it manually. I also manually installed the zcip and tmdns > > > packages, because it seems these are necessary for 9.1 machines to work > > > as simple network clients - if you try and set up a system with > > > drakconnect without these packages installed, it tries to install them > > > (which obviously doesn't work if you only have network sources :>). If > > > using urpmi to update is to become a recommended path, as I believe some > > > people have discussed, I propose it needs some kind of way of taking > > > into account "highly recommended" new packages in the new version like > > > this. > > > > All of this is config files handling (which is not done by urpmi) and > > media management (for avoiding network usage by drakconnect) which need > > doing a little to help it. > > Yes, I know this all isn't strictly urpmi's job. It just strikes me as > an area urpmi could get some neat new features to help with upgrades. > Someone's already suggested a "suggested packages" feature, perhaps we > could implement this somehow, and for instance kdebase could "suggest" > galaxy-kde, which would help upgrades. I guess how this would work would > go: > > urpmi kdebase-kdm > > <normal urpmi stuff> > Package kdebase-kdm suggests package galaxy-kde. Suggested packages are > not required but may provide useful or recommended features. Install > galaxy-kde? (Y/n) > > Or something like that, anyway. :). It's an idea.
ERK! replying to myself, sorry. Just to say, obviously my brain wasn't working when I wrote this - of course I meant just "kdebase", not "kdebase-kdm". -- adamw
