1 |
On Thu, 21 Mar 2013 10:59:49 +0400 |
2 |
"Nikolaj Sjujskij" <sterkrig@×××××××.com> wrote: |
3 |
|
4 |
> Den 2013-03-20 23:03:43 skrev Michał Górny <mgorny@g.o>: |
5 |
> |
6 |
> > On Wed, 20 Mar 2013 15:10:18 +0400 |
7 |
> > "Nikolaj Sjujskij" <sterkrig@×××××××.com> wrote: |
8 |
> > |
9 |
> >> Den 2013-03-18 02:33:50 skrev Michał Górny <mgorny@g.o>: |
10 |
> >> |
11 |
> >> > The PYTHON_COMPAT_OVERRIDE can be set in the environment to enforce |
12 |
> >> > a different set of Python implementations than one being intersection |
13 |
> >> > of PYTHON_COMPAT and PYTHON_TARGETS. |
14 |
> >> > |
15 |
> >> > Due to technical limitations, the variable influences only the list |
16 |
> >> > of implementations actually used. USE flags, dependencies and other |
17 |
> >> > metadata variables are not modified. |
18 |
> >> Push it to tree, please, I'd like to test it :) |
19 |
> > |
20 |
> > Pushed :). |
21 |
> Yup, works fine: https://bugs.gentoo.org/show_bug.cgi?id=462566 |
22 |
> One minor thing. I have PYTHON_TARGETS="python2_7 python3_3" in make.conf, |
23 |
> pylint ebuild has PYTHON_COMPAT=( python2_{5,6,7} python{3_1,3_2} ). I |
24 |
> expected `PYTHON_COMPAT_OVERRIDE="python3_3" emerge -1 pylint` to install |
25 |
> pylint for both 2.7 and 3.3. Of course, it's "OVERRIDE", not "UPDATE", but |
26 |
> still. |
27 |
> A minor thing, really, and I won't insist on changing this behaviour. |
28 |
> Thanks in any case :) |
29 |
|
30 |
I've decided to go this way since you can't change the IUSE. Therefore, |
31 |
you can't really control the enabled implementations via USE flags. If |
32 |
it worked like you suggested, some of the implementations would respect |
33 |
USE flags and some other wouldn't -- that would be confusing. |
34 |
|
35 |
-- |
36 |
Best regards, |
37 |
Michał Górny |