| 1 |
On Sun, Aug 16, 2015 at 9:47 AM, "Paweł Hajdan, Jr." |
| 2 |
<phajdan.jr@g.o> wrote: |
| 3 |
> On 8/16/15 3:29 PM, Rich Freeman wrote: |
| 4 |
>> They are deprecated already: |
| 5 |
>> https://gitweb.gentoo.org/repo/gentoo.git/tree/metadata/layout.conf |
| 6 |
>> |
| 7 |
>> Deprecated means stop adding them, and move away from them. Repoman |
| 8 |
>> will give you a warning about them. |
| 9 |
> |
| 10 |
> Is anything blocking deprecating EAPI4 in the same way? |
| 11 |
> |
| 12 |
|
| 13 |
Not that I'm aware of, and it is probably something worth discussing |
| 14 |
at this point. Moving to EAPI5 has some user-visible improvement for |
| 15 |
many packages, like slot-operator dependencies. EAPI6 will also have |
| 16 |
a user-visible improvement in forced support for user-patching for all |
| 17 |
ebuilds (any ebuild can support user-patches now, but it isn't |
| 18 |
mandatory). So, more than in the past it is useful to nudge devs |
| 19 |
along to the most recent EAPIs (in the past they've been more about |
| 20 |
maintainability and less user-visible). |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives