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