1 |
On Fri, 23 Nov 2012 14:32:18 +0100 |
2 |
Thomas Sachau <tommy@g.o> wrote: |
3 |
|
4 |
> Michał Górny schrieb: |
5 |
> > It's based on the PYTHON_SINGLE_TARGET variable concept. For that |
6 |
> > reason, I used '-single' in the name. If someone could come up with |
7 |
> > a better name, I'd be happy to use it. |
8 |
> > |
9 |
> > It's used on top of python-r1. Similarly, you use ${PYTHON_DEPS} in your |
10 |
> > RDEP/DEP; [${PYTHON_USEDEP}] can be used to depend on single- and multi- |
11 |
> > implementation packages. |
12 |
> > |
13 |
> > pkg_setup() is exported. It finds the enabled implementation, and |
14 |
> > exports EPYTHON and PYTHON. |
15 |
> > |
16 |
> |
17 |
> Maybe this is just a bit misleading, but let me ask to clarify this: |
18 |
> |
19 |
> What exactly does "it finds the enabled implementation" mean? Is it |
20 |
> defined by the user (via a USE flag) or based on eselect-python target? |
21 |
|
22 |
Was in the last thread. Chosen through PYTHON_SINGLE_TARGET USE flag. |
23 |
|
24 |
> How does a dev define the implementation to be used and how does the |
25 |
> package manager output look like for sucht a package? |
26 |
|
27 |
I don't understand the first question. |
28 |
|
29 |
The output is, shortly saying, ugly: |
30 |
|
31 |
[ebuild R ] net-libs/libproxy-0.4.10-r1::gentoo-cvs USE="webkit* -gnome -kde -mono -networkmanager -perl -python* -spidermonkey {-test}" PYTHON_SINGLE_TARGET="python2_7* -python2_6*" PYTHON_TARGETS="python2_6 python2_7" 0 kB |
32 |
|
33 |
-- |
34 |
Best regards, |
35 |
Michał Górny |