top-posting me too to avoid more confusion, sorry Se my other reply to this thread, upgrading in place an old gentoo install is nearly impossible, it's so bad that glibc breakage can occour, that require a knowledge of the system so high that everything else become nuances of a vague problem. Tell everyone that it's not possible to upgrade a 2009 system id more honest and free everybody from forever compatibility slavery.
To be able to upgrade a gentoo installation as old as five years is interesting and valuable but require an effort that has yet to be made. P.S. I'm neutral about EAPI 1 deprecation, just stating that forever support is a chimera right now 2012/3/11 Richard Yao <r...@cs.stonybrook.edu>: > These must be maintained indefinitely to provide an upgrade path for > older Gentoo Linux installations. It is rare, but people do upgrade > old installs from time to time. Without some EAPI=1 packages, there is > no path for people to use to upgrade. > > On Sun, Mar 11, 2012 at 8:01 AM, Pacho Ramos <pa...@gentoo.org> wrote: >> After reading previous discussion: >> http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567.html >> >> Looks like preventing NEW commits from using eapi1 (via repoman) could >> be done without major issues. This could even being done also for eapi2 >> as it's close enough to eapi3, but I don't have a strong opinion about >> eapi2 deprecation (personally, I try to always use latest eapi if eclass >> allows me to do so). >> >> Any thoughts on this? >> >> Thanks >
