1 |
On Mon, 29 Oct 2012 15:45:01 +0100 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
|
4 |
> Since some ebuilds are using that variable already and we still didn't |
5 |
> inform most of our users if and how they should set it, I'd like to |
6 |
> commit the following news item: |
7 |
|
8 |
Thank you for all your suggestions, and especially Duncan for wording |
9 |
the hardest paragraph for me ;). I've also tried to make the remaining |
10 |
ones clearer. |
11 |
|
12 |
Title: PYTHON_TARGETS deployment |
13 |
Author: Michał Górny <mgorny@g.o> |
14 |
Content-Type: text/plain |
15 |
Posted: 2012-10-29 |
16 |
Revision: 1 |
17 |
News-Item-Format: 1.0 |
18 |
|
19 |
Recently, a few new Python eclasses were deployed. As ebuilds migrate, |
20 |
the way they support multiple Python implementations will change. |
21 |
The previous method built Python modules for all currently installed |
22 |
Python implementations. The new one uses the PYTHON_TARGETS USE flags to |
23 |
explicitly name the implementations the modules shall be built for. |
24 |
|
25 |
If you are running a modern system with Python 2.7 & 3.2 being the only |
26 |
installed Python implementations, then you don't have to do anything. |
27 |
The defaults will simply fit you, and let you keep your system |
28 |
up-to-date when new Python versions are deployed. |
29 |
|
30 |
However, if you'd like to use another set of Python implementations, you |
31 |
will want to set PYTHON_TARGETS in your make.conf file appropriately. |
32 |
This variable names the enabled implementations in the standard way |
33 |
common to all USE_EXPAND variables. |
34 |
|
35 |
For example, a setup enabling all major Python implementations would |
36 |
look like: |
37 |
|
38 |
PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5" |
39 |
|
40 |
The variable should list all Python implementations which are going to |
41 |
be used on the system; missing a particular value there will result |
42 |
in missing Python modules. |
43 |
|
44 |
A complete list of all possible values can be obtained using a command |
45 |
equivalent to the following: |
46 |
|
47 |
emerge -1pv dev-python/python-exec |
48 |
|
49 |
-- |
50 |
Best regards, |
51 |
Michał Górny |