| 1 |
On Mon, Jun 27, 2011 at 21:31, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> Working targets. USE_PYTHON is junk. What python.eclass does now with |
| 3 |
> ABIs is a PITA, and requires manually providing a lot of redudant |
| 4 |
> information (namely, RESTRICT_PYTHON_ABIS). |
| 5 |
|
| 6 |
Please clarify *why* it is a PITA, and what information is redundant. |
| 7 |
|
| 8 |
> Right now, each ebuild has to provide the same information in |
| 9 |
> PYTHON_DEPEND and RESTRICT_PYTHON_ABIS. Moreover, if an ebuild |
| 10 |
> supports, say, py3 and its dependency doesn't, the ebuild has to |
| 11 |
> restrict py3 too. |
| 12 |
|
| 13 |
I'll grant you that PYTHON_DEPEND and RESTRICT_PYTHON_ABIS seem |
| 14 |
redundant, we could probably fix that. |
| 15 |
|
| 16 |
> I'd like to see that fixed somehow. I'd like to set a single supported |
| 17 |
> Python version information in an ebuild, and let the dependency |
| 18 |
> resolver handle everything else. |
| 19 |
|
| 20 |
That would be bad; it's common and useful to have packages installed |
| 21 |
in both 2.6 and 2.7 (and even 3.1). |
| 22 |
|
| 23 |
Cheers, |
| 24 |
|
| 25 |
Dirkjan |
Archives