-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> long story short having a portage-20130126.tar.bz2 snapshot >> (before the EAPI 5 switch) greatly simplified the upgrade of an >> old server on a client.
I have done the switch to the current profile+portage on many server recently and i don't think that it is neccessary to keep an old portage snapshot around. Updating from old portage versions or profiles isn't fun but it basically boils down to - - Update python to latest 2.7/3.2 - - Run python-updater and select 2.7/3.2 as the main python version - - Drop old python version - - Update Portage, layman, eix - - Switch to the current profile - - Update the rest If you switched to the new profile with an old portage too early (happens to me *twice*), you will get at some point many blockers due to EAPI=5 and have to hack either the ebuilds or update portage manually. > The goal is to be able to update a device for a year. Not updating > at least once a year is not supportable, and should be discouraged. > I'm sorry for your pain, I really am, but I hope that it pushes you > to update twice a year instead of zero times. I think that even half a year is a very long period in Gentoo. Updating the core packages (portage, openrc, udev, etc.) on a (bi-)monthly basis makes sure that you don't run in such troubles. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJShFOwAAoJEKCEBkJ3xQHtVB8H/jTp17a1nuQP8N8wajkG90/o pc353PvxW/JgRYBKBrdmWEqW0dS1wRsdbPVnZuOkWpWw4CXbXc7fTJ6gualYUx8L 6FgwsGwWRu/WpSVIvu9gYmtc+yWSPv3YBVmdi0d0KfzUU10sAZn74+0tHUKaSglE TkunxAB6YSGRYj4VC6ZfaFK38gq5owgyzNjLa90rEPY4QFuTum16Y7Jr6RKtQGa1 LuJygufXPGxasW001dUmVTyQUH+vOxF3nWWaaj92zgGf33t67GeY6MMSnwFVXnnr AYlHykYQr0RmPGmZShAnhr8B3HL7vDdm0CXzmg23noyiT67RqRXOqDJxwTw+29o= =jQEK -----END PGP SIGNATURE-----
