| 1 |
On Sun, Apr 17, 2016 at 10:37 AM, Ian Stakenvicius <axs@g.o> wrote: |
| 2 |
> |
| 3 |
>> On Apr 17, 2016, at 10:13 AM, Mike Gilbert <floppym@g.o> wrote: |
| 4 |
>> |
| 5 |
>> The xorg-2 eclass currently uses the deprecated autotools-utils and |
| 6 |
>> autotools-multilib eclasses, which are banned in EAPI 6. |
| 7 |
>> |
| 8 |
>> This patchset attempts to remove any trace of autotools-utils from ebuilds |
| 9 |
>> using xorg-2. |
| 10 |
>> |
| 11 |
>> Note that I am touching stable ebuilds here to avoid forking an "xorg-3" |
| 12 |
>> eclass. If there is a strong feeling that this is too dangerous, I can alter |
| 13 |
>> my approach. I have build tested most packages using xorg-2, and only a few |
| 14 |
>> had issues. |
| 15 |
>> |
| 16 |
> |
| 17 |
> Although I commend you for these efforts, given that this deprecation is also linked to EAPI6, why not instead bump to XORG-3 requiring EAPI6, take advantage of all the simplifications, and this will allow/enforce migration of all the ebuilds as well in turn? |
| 18 |
> |
| 19 |
> It would be nice for instance to drop the epatch stuffs at the same time, if we could... |
| 20 |
> |
| 21 |
|
| 22 |
If the x11 team wants to go that way, that's fine. It's just a lot |
| 23 |
more work to update all the ebuilds, so I would need people to help |
| 24 |
out. |
Archives