| 1 |
El dom, 11-03-2012 a las 13:01 +0100, Pacho Ramos escribió: |
| 2 |
> After reading previous discussion: |
| 3 |
> http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567.html |
| 4 |
> |
| 5 |
> Looks like preventing NEW commits from using eapi1 (via repoman) could |
| 6 |
> be done without major issues. This could even being done also for eapi2 |
| 7 |
> as it's close enough to eapi3, but I don't have a strong opinion about |
| 8 |
> eapi2 deprecation (personally, I try to always use latest eapi if eclass |
| 9 |
> allows me to do so). |
| 10 |
> |
| 11 |
> Any thoughts on this? |
| 12 |
> |
| 13 |
> Thanks |
| 14 |
|
| 15 |
Well, the reasons for me preferring to not allow *new* ebuilds to use |
| 16 |
eapi1 is to try to move to use things like, for example, |
| 17 |
src_prepare/src_configure phases. I guess that phases were included for |
| 18 |
some "technical" reasons and, then, I think we should try to use them if |
| 19 |
possible install of still adding NEW ebuilds using old eapi0/1 way of |
| 20 |
doing things |
Archives