1 |
On Mon, Oct 29, 2012 at 10:45 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
> Hello, |
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 |
> Title: PYTHON_TARGETS deployment |
9 |
> Author: Michał Górny <mgorny@g.o> |
10 |
> Content-Type: text/plain |
11 |
> Posted: 2012-10-29 |
12 |
> Revision: 1 |
13 |
> News-Item-Format: 1.0 |
14 |
> |
15 |
> Lately, a new Python eclasses were deployed and the way of supporting |
16 |
> multiple Python implementations changes with ebuilds being migrated |
17 |
> to them. While before the implementations being installed were used |
18 |
> by default, the migrated packages will instead use explicit choice based |
19 |
> on PYTHON_TARGETS USE flags. This may require action from some of our |
20 |
> users. |
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 |
24 |
> will fit you. |
25 |
> |
26 |
> Otherwise, you will want to set PYTHON_TARGETS in your make.conf file. |
27 |
> This is a regular USE_EXPAND variable listing requested Python |
28 |
> implementations like: |
29 |
> |
30 |
> PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5" |
31 |
> |
32 |
> The variable should list all requested Python implementations. |
33 |
> A complete list of possible values can be obtained using a command like: |
34 |
> |
35 |
> emerge -1pv dev-python/python-exec |
36 |
> |
37 |
|
38 |
Good idea to inform users. |
39 |
|
40 |
Is there a way to have this news item go away, say after a year or so? |
41 |
Every time I do a fresh install, I get hit with a couple of |
42 |
"perpetual" news items, and it is a little annoying. |