| 1 |
On Tue, Mar 6, 2018 at 1:35 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> On Tue, Mar 6, 2018 at 4:17 PM, Andreas K. Huettel <dilfridge@g.o> wrote: |
| 3 |
>> |
| 4 |
>> Is it worth the effort? Yes, see below. |
| 5 |
>> Is it a high priority task? No. |
| 6 |
>> |
| 7 |
> |
| 8 |
> It sounds like all that has been done is to log a tracker and create |
| 9 |
> some bugs. That is hardly a major burden on anybody. If it nudges |
| 10 |
> people to bump the EAPI when they're doing other work so much the |
| 11 |
> better, but there doesn't seem to be a drop-dead date yet. |
| 12 |
> |
| 13 |
> If devs don't want to think about EAPI cleanup they don't have to right now. |
| 14 |
|
| 15 |
No, not true. Look at the blocking bugs. We're asking arch teams to |
| 16 |
retest and restabilize ebuilds whose only difference is the EAPI bump. |
Archives