On Tuesday 03 May 2005 09:10, Chris Gianelloni wrote: > I think an easier solution would be a portage rescue set of profiles. > These would be minimal profiles not designed for actual use, but only > for performing a portage update for those people that lag too far > behind. The idea would be a very tiny profile, per arch, that is not > cascaded.
Perhaps another solution would be to create a system with archives of the profiles and packages necessary to do an upgrade from an old portage and profile to a new portage and profile, seeing as portage has circular effective dependencies on at least the tree and python, perhaps other stuff as well. This could be some sort of script which downloads the archive, then upgrades, one major shift at a time. Once said system is in place, notices could be put in the deprecated files (and of course the homepage) to that effect, and the old profiles removed from the main tree after a while. Just a thought. --electronerd
pgptovAAYBmCE.pgp
Description: PGP signature
