1 |
Dnia 2013-10-20, o godz. 10:53:34 |
2 |
Mike Gilbert <floppym@g.o> napisał(a): |
3 |
|
4 |
> On Sun, Oct 20, 2013 at 3:36 AM, Michał Górny <mgorny@g.o> wrote: |
5 |
> > As described in the ml, the new function does: |
6 |
> > |
7 |
> > * in python-any-r1, choose and set up the best installed impl, |
8 |
> > |
9 |
> > * in python-single-r1, read PYTHON_SINGLE_TARGET and set it up, |
10 |
> > |
11 |
> > * in python-r1, call python_export_best + python_wrapper_setup. |
12 |
> > |
13 |
> > In other words, it's a common way of getting Python build environment |
14 |
> > set up in the ebuild scope. |
15 |
> |
16 |
> Invoking python_setup from pkg_setup in any eclass seems sub-optimal; |
17 |
> especially so in python-any-r1. However, I realize there isn't a great |
18 |
> place to put it. |
19 |
|
20 |
I don't understand. Could you rephrase? |
21 |
|
22 |
-- |
23 |
Best regards, |
24 |
Michał Górny |