| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 29/10/14 02:42 PM, W. Trevor King wrote: |
| 5 |
> On Wed, Oct 29, 2014 at 02:33:47PM -0400, Ian Stakenvicius wrote: |
| 6 |
>> On 29/10/14 02:25 PM, W. Trevor King wrote: |
| 7 |
>>> Personally, I'd prefer to stick with my existing |
| 8 |
>>> PYTHON_SINGLE_TARGET. If a package doesn't like that, I can |
| 9 |
>>> think harder about whether or not I actually need the package. |
| 10 |
>>> My Docker images [1], for example, are single-Python |
| 11 |
>>> implementations and I don't want to pull in another Python |
| 12 |
>>> accidentally. |
| 13 |
>> |
| 14 |
>> This change will not pull in extra python versions, it just |
| 15 |
>> changes the python-single-r1 inheriting ebuilds so that they rely |
| 16 |
>> on the values set in PYTHON_TARGETS for resolution, instead of |
| 17 |
>> PYTHON_SINGLE_TARGET. |
| 18 |
> |
| 19 |
> Ah, so it's “feel free to ignore my PYTHON_SINGLE_TARGET”, not |
| 20 |
> “feel free to ignore my PYTHON_TARGETS.” |
| 21 |
|
| 22 |
|
| 23 |
Correct. Apologies for not making that clearer in my original post. |
| 24 |
|
| 25 |
|
| 26 |
> ... That works for me, since I don't care what version of Python a |
| 27 |
> single-implementation package is installed with (as long as it's in |
| 28 |
> my PYTHON_TARGETS and any dependers are satisfied). |
| 29 |
> |
| 30 |
|
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2 |
| 33 |
|
| 34 |
iF4EAREIAAYFAlRRNjwACgkQ2ugaI38ACPAtsAD+LvqjOPXrv1T9IyP3EqTeuqZX |
| 35 |
qO366NnqnlOwgq4wZ3MA/A9znOhCF95vC0DEhh/NtXlxgY16D6cB4Fg2VH4Qp/VN |
| 36 |
=maFF |
| 37 |
-----END PGP SIGNATURE----- |
Archives