| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 10/27/2013 02:30 AM, Mike Gilbert wrote: |
| 5 |
> |
| 6 |
> The (non-)relationship between eselect python and PYTHON_TARGETS |
| 7 |
> is something that would be nice to resolve, but I don't know how to |
| 8 |
> do it. PYTHON_SINGLE_TARGET will probably cause problems if/when |
| 9 |
> packages start supporting python3 only. |
| 10 |
> |
| 11 |
|
| 12 |
I think python-single-r1 is one of the major problems for users, |
| 13 |
because they have to mess with two variables/useflags. Most just put |
| 14 |
PYTHON_SINGLE_TARGET="python3_3" or something in make.conf which then |
| 15 |
again affects all packages and WILL cause blockers/unresolvable deps. |
| 16 |
|
| 17 |
Afair in the very early versions we just picked the "best" |
| 18 |
implementation and were done with it (since a python-single-r1 package |
| 19 |
should not provide modules anyway). |
| 20 |
|
| 21 |
What is wrong with that approach (except that it still causes useless |
| 22 |
rebuilds)? Do users really need that sort of control over non-module |
| 23 |
packages? If they really do, you can still do some additional work and |
| 24 |
make a real python-r1 package out of it. |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 27 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 28 |
|
| 29 |
iQEcBAEBAgAGBQJSbQEKAAoJEFpvPKfnPDWz5vsIAIjvgXeR3bVy5ayT8XpZDjZ1 |
| 30 |
G9hghpRqVr6C4ITTXeFnOQcmOqtcHb2zt6rudgjV8//4H9Vr+ZSqUmPAMaaM7aN6 |
| 31 |
A0ujl6+awMDoK3GUHZ05Hk0W+gy561OkeFpoCMkBZ1Xe31DEo3nnWUktYOfscal6 |
| 32 |
QAWQRUbONX/efoDh0C6WOSMfpgvgMn2TYvem+SOQ7PTiK01rY9Hoy5+JiN1g/e/W |
| 33 |
4dmvmxXMQ8e7n0Ec/L0vtmey4NM6znqMQHzvK6r5Aed/6B1hzwNRvFz0R7QcjjUO |
| 34 |
B/kYopuTOzj8jr52Vl00rFVRP69bMFq1M4lldQiy6dIznOGr8WLX23UhSHS1J30= |
| 35 |
=nAwp |
| 36 |
-----END PGP SIGNATURE----- |
Archives