Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<p>On Sep 20, 2011 1:05 PM, "Patrick Lauer" <<a href="mailto:patrick@g.o">patrick@g.o</a>> wrote:<br>
> Good idea, but won't work retroactively out of the box. So you'd need a helper script to figure out your current state (using portage version and tree snapshot maybe), then prepare the environment to upgrade<br>
> (and how do you handle the "common" case of python 2.5 only which doesn't allow newest portage anyway?)<br>
></p>
<p>Does it really need to be automated? Why not just have a big howto that we append to whenever we break @system upgrades? The top would have a table telling you where to start based on portage version or whatever. </p>
<p>The howto would contain links to portage and bindist snapshots (just what you need to upgrade - maybe binary pkgs, maybe not). Then it would have a list of steps to follow. </p>
<p>If you are three years out of date it would be a long journey, but it should work. I don't think we need to make it a trivial upgrade, just a workable one. </p>
<p>And as far as extracting stage3s go - I've done it before in a pinch, but I usually pick and choose individual files to keep it under control...</p>
<p>Rich</p>
|
|
