| 1 |
Hi, |
| 2 |
|
| 3 |
Just a quick idea: |
| 4 |
|
| 5 |
1. we set default PYTHON_SINGLE_TARGET to 3.* matching PYTHON_TARGETS, |
| 6 |
|
| 7 |
2. python2.7-only ebuilds get implicit 2.7 via axs' patch, |
| 8 |
|
| 9 |
3. py2.7+pypy ebuilds -- we enable 2.7 via package.use. |
| 10 |
|
| 11 |
|
| 12 |
Goals: |
| 13 |
|
| 14 |
a. have as high coverage as possible of ebuilds that can be installed |
| 15 |
with default USE set. |
| 16 |
|
| 17 |
b. Make it cleaner to install py3-only ebuilds. Right now, user gets to |
| 18 |
enable 3.* manually, and then maintain the entry whenever 3.* is |
| 19 |
upgraded to newer version. |
| 20 |
|
| 21 |
c. Improve 2.7+3.* ebuilds by replacing 2.7 with the faster & better |
| 22 |
3.* :). |
| 23 |
|
| 24 |
d. Make it easier to switch 3.* version. When user wants to change it |
| 25 |
from 3.3 to 3.4 or the other way around, he just needs to adjust PST |
| 26 |
and 2.7+pypy ebuilds still work fine. |
| 27 |
|
| 28 |
Your thoughts? |
| 29 |
|
| 30 |
-- |
| 31 |
Best regards, |
| 32 |
Michał Górny |
Archives