| 1 |
These must be maintained indefinitely to provide an upgrade path for |
| 2 |
older Gentoo Linux installations. It is rare, but people do upgrade |
| 3 |
old installs from time to time. Without some EAPI=1 packages, there is |
| 4 |
no path for people to use to upgrade. |
| 5 |
|
| 6 |
On Sun, Mar 11, 2012 at 8:01 AM, Pacho Ramos <pacho@g.o> wrote: |
| 7 |
> After reading previous discussion: |
| 8 |
> http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567.html |
| 9 |
> |
| 10 |
> Looks like preventing NEW commits from using eapi1 (via repoman) could |
| 11 |
> be done without major issues. This could even being done also for eapi2 |
| 12 |
> as it's close enough to eapi3, but I don't have a strong opinion about |
| 13 |
> eapi2 deprecation (personally, I try to always use latest eapi if eclass |
| 14 |
> allows me to do so). |
| 15 |
> |
| 16 |
> Any thoughts on this? |
| 17 |
> |
| 18 |
> Thanks |
Archives