| 1 |
Il 24/08/18 19:08, Mike Gilbert ha scritto: |
| 2 |
> On Fri, Aug 24, 2018 at 10:45 AM Kent Fredric <kentnl@g.o> wrote: |
| 3 |
>> On Fri, 24 Aug 2018 10:27:01 -0400 |
| 4 |
>> Mike Gilbert <floppym@g.o> wrote: |
| 5 |
>> |
| 6 |
>>> If you want to define behavior that can be relied upon in ebuilds, it |
| 7 |
>>> should be specified in PMS. PMS does not define any meaning for the |
| 8 |
>>> "test" USE flag. |
| 9 |
>> We should eschew idealism about how the world *should* behave, and avoid |
| 10 |
>> making portage a steaming garbage heap in order to comply with a |
| 11 |
>> terrible PMS specification of a heavily used feature. |
| 12 |
> Portage still works just fine for most people who would enable |
| 13 |
> FEATURES=test. Stop exaggerating. |
| 14 |
> |
| 15 |
People enabling FEATURES=test on most but not all packages had some |
| 16 |
troubles and they need to disable them in both package.{env,use} |
| 17 |
I'd like to have a flag to reinstate the previous portage behaviour, but |
| 18 |
that's probably too late |
Archives