1 |
On Mon, Oct 29, 2012 at 1:01 PM, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
|
3 |
> Michał Górny posted on Mon, 29 Oct 2012 15:45:01 +0100 as excerpted: |
4 |
> |
5 |
> > Title: PYTHON_TARGETS deployment |
6 |
> |
7 |
> [snip] |
8 |
> |
9 |
> > Lately, a new Python eclasses were deployed and the way of supporting |
10 |
> > multiple Python implementations changes with ebuilds being migrated to |
11 |
> > them. While before the implementations being installed were used by |
12 |
> > default, the migrated packages will instead use explicit choice based on |
13 |
> > PYTHON_TARGETS USE flags. This may require action from some of our |
14 |
> > users. |
15 |
> |
16 |
> That paragraph needs help. Try this: |
17 |
> |
18 |
> Recently, new python eclasses were deployed. As ebuilds migrate, the way |
19 |
> |
20 |
|
21 |
Recently, a new python eclass was deployed. |
22 |
|
23 |
or |
24 |
|
25 |
Recently, a few new python eclasses were deployed. |
26 |
|
27 |
or even |
28 |
|
29 |
Recently, a few python eclasses were deployed. |
30 |
|
31 |
And then capitalize Python. |
32 |
|
33 |
-- |
34 |
:wq |