| 1 |
Den 2012-05-12 14:04:36 skrev Krzysztof Pawlik <nelchael@g.o>: |
| 2 |
|
| 3 |
>>> - uses PYTHON_TARGETS use-expand (no more python-updater, whoooo!) |
| 4 |
>> Hm... Does it require users to maintain correct PYTHON_TARGETS in |
| 5 |
>> make.conf? No default/fallback value? |
| 6 |
> |
| 7 |
> No, I'm a *HUGE* fan of free choice -- I don't know which Python version |
| 8 |
> you want, so select the correct one yourself. It's a one-time choice |
| 9 |
> anyway. |
| 10 |
Just as Michał has pointed it, it is not. |
| 11 |
|
| 12 |
>> It's not big deal, of course, but kind of annoying after so many years |
| 13 |
>> of automatic "build for current Python version unless USE_PYTHON is |
| 14 |
>> set". |
| 15 |
> To me it's an advantage :) |
| 16 |
Why? 90% of users just use latest Python available, i.e. 2.7 and 3.2 at |
| 17 |
the moment, and don't really care about actual versions. |
| 18 |
python.eclass handles this smoothly, probably using eselect'ed versions. |
| 19 |
Only few people (like me) set USE_PYTHON to suit their needs. Why new |
| 20 |
eclass cannot behave in a similar way? Where's the profit? There's open |
| 21 |
bug already: https://bugs.gentoo.org/show_bug.cgi?id=415575 |
Archives