On Fri, 23 Nov 2012 14:32:18 +0100 Thomas Sachau <to...@gentoo.org> wrote:
> Michał Górny schrieb:
> > It's based on the PYTHON_SINGLE_TARGET variable concept. For that
> > reason, I used '-single' in the name. If someone could come up with
> > a better name, I'd be happy to use it.
> >
> > It's used on top of python-r1. Similarly, you use ${PYTHON_DEPS} in your
> > RDEP/DEP; [${PYTHON_USEDEP}] can be used to depend on single- and multi-
> > implementation packages.
> >
> > pkg_setup() is exported. It finds the enabled implementation, and
> > exports EPYTHON and PYTHON.
> >
>
> Maybe this is just a bit misleading, but let me ask to clarify this:
>
> What exactly does "it finds the enabled implementation" mean? Is it
> defined by the user (via a USE flag) or based on eselect-python target?
Was in the last thread. Chosen through PYTHON_SINGLE_TARGET USE flag.
> How does a dev define the implementation to be used and how does the
> package manager output look like for sucht a package?
I don't understand the first question.
The output is, shortly saying, ugly:
[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
--
Best regards,
Michał Górny
signature.asc
Description: PGP signature
