| 1 |
Sent from an iPhone, sorry for the HTML... |
| 2 |
|
| 3 |
> On Feb 7, 2015, at 5:01 PM, Michał Górny <mgorny@g.o> wrote: |
| 4 |
> |
| 5 |
> Dnia 2015-02-07, o godz. 16:54:54 |
| 6 |
> Mike Gilbert <floppym@g.o> napisał(a): |
| 7 |
> |
| 8 |
>>> On Sat, Feb 7, 2015 at 3:38 PM, Michał Górny <mgorny@g.o> wrote: |
| 9 |
>>> Hi, |
| 10 |
>>> |
| 11 |
>>> Just a quick idea: |
| 12 |
>>> |
| 13 |
>>> 1. we set default PYTHON_SINGLE_TARGET to 3.* matching PYTHON_TARGETS, |
| 14 |
>>> |
| 15 |
>>> 2. python2.7-only ebuilds get implicit 2.7 via axs' patch, |
| 16 |
>>> |
| 17 |
>>> 3. py2.7+pypy ebuilds -- we enable 2.7 via package.use. |
| 18 |
>> |
| 19 |
>> Does #3 actually work if PYTHON_SINGLE_TARGET=python3_3 is in |
| 20 |
>> make.conf? I forget what our findings were on this. |
| 21 |
> |
| 22 |
> I forgot as well. Though I think we were trying IUSE defaults then. |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
Sorry for the month long delay; yes, this works. Indeed that was the point of the patch, to allow PYTHON_SINGLE_TARGET to be global and something other than python2_7 when a 2.7-only package is installed. |
Archives