Hi to all
As most of us know, the first step in upgrading 7.2 is rpm upgrading to 4.x
Doing this involves a lot of other packages, and the possible shortcut ways
are --forcing as dependencies as possible or directly jumping to install
cooker, as someone said. But cooker is unstable by definition, so this is an
unwise move if the box is to be used for everyday work. By the way the 
starting point is widely uncertain, as every normal installation is tailored 
its own way. I had good results in the last weeks starting new minimal 
installations and then upgrading them in the most complete way following
what dependencies required. It was a very cumbersome work, but at the end
I had a working system with rpm 4.x, XFree 4.0.2,KDE2,kernel 2-4.1-3 and
all the related goodies, that at present looks stable and with minor problems.
It required downloading some 250-300 meg, but far less than cooker.
Now I come to the point: don't you think it would be practical making another
directory on cooker mirrors containing all and only one stable version of each
package needed for such an upgrade? It wouldn't be necessary to maintain
this directory, as every upgraded system could then be feeded by cooker
itself. Moreover, adding installation files could lead to a "7.2-b" that I 
think will cause a lot of people to feel very happy as all that they have to 
do is downloading and installing. Am I wrong?

Best regards
Alberto Vorano

Reply via email to