Re: upgrading 7.2+rawhide -> rh8.0 via grab

On Wed, 2002-10-09 at 15:05, Greg Kurtzer wrote:
> Basically, this is very risky and unless I can figure out (or someone can
> spec it out to me (in pseudo code please)) how to do this, we will have to
> rely on the package automatically figuring them selves out.

yep this has come up before...and i dont have any new ideas...but I'll
recap my thoughts for anyone new in the list that might be inspired by
them.  Brainstorming is good....feel free to bring up wacky ideas, cuz
there might be something inspiring in them.

A) tiered servers: so you can select to prefer the packages on one
server over another, everyday use example using high 1-9 low for
priority

1) galeon's ftp site
2) ximian
3) redhat updates
4) redhat base

this would prefer the most uptodate package from galeons ftp site, then
xims galeon, then redhat's updates, then redhats base....when looking up
all dependancies.

so in the case of moving from redhat 7.2 to redhat 8.0

1) 8.0 updates
2) 8.0 base
3) 7.2 updates
4) 7.2 base

if there is a dependancy conflict grab looks to the 8.0 servers first to
fill them.


B) forming some sort of hand built set of fake rpms that do rpm database
manipulations that allow the mating of redhat 7.2 to redhat 8.0,
manipulating the rpmdb per dependancy issue to facilite a clean
upgrade.  Put them all in a repository, run then remove those rpms after
the upgrade.

Things still aren't clearly worked out in my head how to go about this
to the point where I can give an example agorithm.

-jef

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA9pJElrWLDmRitRZURAmhhAKCDzdbQ8PTrF/1oe/jQAOjfxHewdACdExK/
1Mp1Jujs4r8FEhGVKuxfdpM=
=AoRf
-----END PGP SIGNATURE-----