| 1 |
Il 03/04/2013 17:22, Zac Medico ha scritto: |
| 2 |
> On 04/03/2013 02:31 AM, vivo75@×××××.com wrote: |
| 3 |
>> 3 years are pratically more than you can ever hope to support without |
| 4 |
>> adding manpower dedicated to keep backward compatibility. |
| 5 |
>> |
| 6 |
>> Previous reasoning based on the assumption that a) newer api are better |
| 7 |
>> b) less of them is better c) not being able to upgrade portage mean a |
| 8 |
>> not upgradable/modifiable gentoo install. |
| 9 |
> It's a little bit silly to try to maintain backward compatibility for |
| 10 |
> more than 3 years when you can easily revive an old system by bind |
| 11 |
> mounting it into a fresh chroot as suggested here: |
| 12 |
> |
| 13 |
> https://bugs.gentoo.org/show_bug.cgi?id=457148 |
| 14 |
indeed that look a very good solution, this would also keep Gentoo |
| 15 |
rolling and avoid support EAPI=0 for the next X years (or at least |
| 16 |
having a deprecation time much shorter than 5 years)? Hopefully so. |
| 17 |
|
| 18 |
New ebuilds should be written using newer EAPI waiting for the shrinking |
| 19 |
number of old ones to being ported by some superhuman in his free time. |
Archives