Re: upgrading from rh7.2 to 7.3 -- dependency problem

so an algorithm you are looking to have is like this:

1) select packages
2) find deps
3) if deps unresolved check for extra packages to fill deps...including
	missing files
4) download full list of packages
5) attempt to install
6) if there is a conflict with an upgrade package and an installed
package...check the grab provides database to find appropriate upgrades
for the packages invovled in the conflict....repeat to step 2 for the
new packages

Now this sounds really good but how far do you let grab try to do this. 
I really dont want grab to do this level of automagical configuration,
becuase I don't trust situations when there are conflicts at the file
level that don't get caught at the dep resolution level.

For instance....trying to use the newest xscreensaver from rawhide has a
file conflict with the control-center package from redhat 7.3..becuase
the xscreensaver capplet was moved into the xscreensaver package in
rawhide.  Following the algorithm above grab would see the conflict and
then try to upgrade control-center...but to do that you have to have ALL
the gnome2 stuff installed...which is total overkill for the situation. 
You dont need to have a gnome2 desktop with the gnome2 control center to
run the new xscreensaver.

These kind of conflicts should never be seen if you stick updates for
your base distro.  But if you are going to try to upgrade selectively
from a newer base distro tree...you will always run into these
issues...and depending on the intent of the upgrade...you may not want
to pull in 70+ packages just becasue of a rather simple and harmless
file conflict.  You can quickly spiral into a situation were you have to
upgrade a large chunk of packages...packages you don't necessarily want
to upgrade.


-jef


On Mon, 2002-08-12 at 15:01, Carl Wilhelm Soderstrom wrote:
> I was expecting that since the packages being installed complained about
> missing a file; that grab could just search through the new packages (which
> should be in the database now, right?), and find that file; even if it
> wasn't in the package it used to be in.