1 |
On Sat, 2018-08-25 at 01:14 +0200, Francesco Riosa wrote: |
2 |
> Il 24/08/18 19:08, Mike Gilbert ha scritto: |
3 |
> > On Fri, Aug 24, 2018 at 10:45 AM Kent Fredric <kentnl@g.o> wrote: |
4 |
> > > On Fri, 24 Aug 2018 10:27:01 -0400 |
5 |
> > > Mike Gilbert <floppym@g.o> wrote: |
6 |
> > > |
7 |
> > > > If you want to define behavior that can be relied upon in ebuilds, it |
8 |
> > > > should be specified in PMS. PMS does not define any meaning for the |
9 |
> > > > "test" USE flag. |
10 |
> > > |
11 |
> > > We should eschew idealism about how the world *should* behave, and avoid |
12 |
> > > making portage a steaming garbage heap in order to comply with a |
13 |
> > > terrible PMS specification of a heavily used feature. |
14 |
> > |
15 |
> > Portage still works just fine for most people who would enable |
16 |
> > FEATURES=test. Stop exaggerating. |
17 |
> > |
18 |
> |
19 |
> People enabling FEATURES=test on most but not all packages had some |
20 |
> troubles and they need to disable them in both package.{env,use} |
21 |
> I'd like to have a flag to reinstate the previous portage behaviour, but |
22 |
> that's probably too late |
23 |
> |
24 |
|
25 |
That was a bug in Portage and AFAIK it has been fixed. It would be nice |
26 |
if people didn't add extra hacks to workaround bugs that no longer |
27 |
exist. |
28 |
|
29 |
-- |
30 |
Best regards, |
31 |
Michał Górny |