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