| 1 |
On 28/07/13 05:07 PM, Walter Dnes wrote: |
| 2 |
> On Sat, Jul 27, 2013 at 09:59:38AM +0200, Ulrich Mueller wrote |
| 3 |
>>>>>>> On Sat, 27 Jul 2013, Leho Kraav wrote: |
| 4 |
>> |
| 5 |
>>> php5-5 vs python2_7 |
| 6 |
>>> Why, how did that happen? |
| 7 |
>> |
| 8 |
>> Using the hyphen is cleaner, because the underscore is used as the |
| 9 |
>> separator for USE_EXPAND. |
| 10 |
>> |
| 11 |
>> (OTOH, as long a nobody will introduce a PYTHON_TARGETS_PYTHON2 |
| 12 |
>> variable, python2_7 will also work fine.) |
| 13 |
> |
| 14 |
> Out of sheer curiousity, why does make.conf need all 3 of... |
| 15 |
> |
| 16 |
> PYTHON_SINGLE_TARGET="python2_7" |
| 17 |
|
| 18 |
Because some packages only accept a single version of Python. e.g. |
| 19 |
Blender, systemd. I think this also applies to the default Python |
| 20 |
version for packages that install executables. |
| 21 |
|
| 22 |
> PYTHON_TARGETS="python2_7" |
| 23 |
|
| 24 |
Because the Python ABI [*] requires different libraries to be built for |
| 25 |
different versions and installed in different places. /usr/lib/python?.? |
| 26 |
|
| 27 |
[*] not really a binary interface, but let's call it that |
| 28 |
> USE_PYTHON="2.7" |
| 29 |
|
| 30 |
This is deprecated, AFAIK and used for old packages that do not support |
| 31 |
PYTHON_TARGETS. (something to do with EAPI or eclass or something like that) |
Archives