| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
- -----BEGIN PGP SIGNED MESSAGE----- |
| 5 |
Hash: SHA256 |
| 6 |
|
| 7 |
On 06/09/12 04:26 PM, Michał Górny wrote: |
| 8 |
|
| 9 |
|
| 10 |
Not sure; you think of so many different things.. :D |
| 11 |
|
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
I wanted it to be short -- this is a convenience variable to be used |
| 16 |
in *DEPEND; and since it contains Python Target Use Dependencies, i |
| 17 |
figured the acronym was the best way to go.. |
| 18 |
|
| 19 |
PS, '@INTERNAL' is probably not a good tag to set here but i couldn't |
| 20 |
find documentation on what tags were available; if there's a @READONLY |
| 21 |
or @CONSTANT that would be best. |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
The 'for impl in ${PYTHON_COMPAT}' loop is actually run in global |
| 26 |
scope later, to set *DEPEND on each python implementation; i haven't |
| 27 |
checked but it's possible it can be done there. Also, other bits are |
| 28 |
already using temp variables in global scope. Also2, since this var |
| 29 |
needs to be substituted directly into atoms of the ebuild's *DEPEND, |
| 30 |
imo it needs to be in global scope as well |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
Could be, yes. I had thought to set it before the check as |
| 37 |
PYTHON_COMPAT itself is assigned (if unset) before the check. |
| 38 |
- -----BEGIN PGP SIGNATURE----- |
| 39 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 40 |
|
| 41 |
iF4EAREIAAYFAlBJCTUACgkQ2ugaI38ACPD3TwEAj1rtDO1Rpbmf0g+nU+oHTj5Y |
| 42 |
HIFVsn+bzbx+CB1xU5QBAKxXx5p33y4dhk03zM1VjRWM5J9QdC/uDGq42yapnfdd |
| 43 |
=hm2B |
| 44 |
- -----END PGP SIGNATURE----- |
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 47 |
|
| 48 |
iF4EAREIAAYFAlBJCrMACgkQ2ugaI38ACPAZjwD+PsGxG64rhKM5vmSO+g9Gc1Ij |
| 49 |
N62tR4dar4zGlIGwwfUA/0JH62LPRO/sv6BsvAHWRfXuuU4tkYotY2m7yx5LF6sH |
| 50 |
=Ff8b |
| 51 |
-----END PGP SIGNATURE----- |
Archives