1 |
On Thu, 14 Mar 2013 17:10:26 +0400 |
2 |
"Nikolaj Sjujskij" <sterkrig@×××××××.com> wrote: |
3 |
|
4 |
> Den 2013-03-13 23:49:33 skrev Michał Górny <mgorny@g.o>: |
5 |
> |
6 |
> > It couldn't work properly, so I withdrawn it. The major problem is that |
7 |
> > metadata becomes affected by environmental variables. |
8 |
> > |
9 |
> > Sadly, portage can't handle that nicely. Usually, it just results in |
10 |
> > portage 'sticking' with one particular set of USE flags on the package |
11 |
> > and trying to use the other one at the same time. In other words, a lot |
12 |
> > of random behavior and QA warnings. |
13 |
> > |
14 |
> > Probably, the nearest thing that could work is PYTHON_COMPAT_OVERRIDE |
15 |
> > which doesn't use the USE flags but instead forces all impls listed. |
16 |
> I see... Well, that's unfortunate, I hoped to test pylint with it, |
17 |
> hacking ebuild just for changing PYTHON_COMPAT isn't much fun. |
18 |
|
19 |
Do you consider it useful enough if PYTHON_COMPAT_OVERRIDE affected |
20 |
the build process only? Most importantly, visible USE flags |
21 |
and dependency resolution wouldn't be affected. |
22 |
|
23 |
I asked Zac about a possibility of disabling cache conditionally |
24 |
to a variable but I don't think that reached anywhere. |
25 |
|
26 |
-- |
27 |
Best regards, |
28 |
Michał Górny |