| 1 |
Michał Górny posted on Mon, 29 Oct 2012 15:45:01 +0100 as excerpted: |
| 2 |
|
| 3 |
> Title: PYTHON_TARGETS deployment |
| 4 |
|
| 5 |
[snip] |
| 6 |
|
| 7 |
> Lately, a new Python eclasses were deployed and the way of supporting |
| 8 |
> multiple Python implementations changes with ebuilds being migrated to |
| 9 |
> them. While before the implementations being installed were used by |
| 10 |
> default, the migrated packages will instead use explicit choice based on |
| 11 |
> PYTHON_TARGETS USE flags. This may require action from some of our |
| 12 |
> users. |
| 13 |
|
| 14 |
That paragraph needs help. Try this: |
| 15 |
|
| 16 |
Recently, new python eclasses were deployed. As ebuilds migrate, the way |
| 17 |
they support multiple python implementations will change. The previous |
| 18 |
method built support for all installed python implementations. The new |
| 19 |
method uses the PYTHON_TARGETS USE flags to explicitly name the |
| 20 |
implementations that support should be built for. |
| 21 |
|
| 22 |
> If you are running a modern system with Python 2.7 & 3.2, and you didn't |
| 23 |
> set USE_PYTHON, then you don't have to do anything. The defaults will |
| 24 |
> fit you. |
| 25 |
|
| 26 |
Fewer changes in this paragraph. Try this: |
| 27 |
|
| 28 |
If you are running a modern system with Python 2.7 and 3.2 and you |
| 29 |
haven't set USE_PYTHON, you don't need to do anything. The defaults will |
| 30 |
continue to work just as they have. |
| 31 |
|
| 32 |
|
| 33 |
The rest of it looks good to me. Extra points for the specific examples, |
| 34 |
both of PYTHON_TARGETS and of a suitable command-line to get a list of |
| 35 |
all possibilities. =:^) |
| 36 |
|
| 37 |
-- |
| 38 |
Duncan - List replies preferred. No HTML msgs. |
| 39 |
"Every nonfree program has a lord, a master -- |
| 40 |
and if you use the program, he is your master." Richard Stallman |
Archives