| 1 |
On Fri, Jul 19, 2013 at 12:10 PM, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
> On Fri, 19 Jul 2013 18:05:35 +0200 |
| 4 |
> Michał Górny <mgorny@g.o> wrote: |
| 5 |
>> > So why are these features behind use flags? |
| 6 |
>> |
| 7 |
>> For compatibility with ${PYTHON_USEDEP}. |
| 8 |
> |
| 9 |
> Why not fix PYTHON_USEDEP? |
| 10 |
> |
| 11 |
|
| 12 |
An alternative would be insert some logic in the python eclasses to |
| 13 |
parse PYTHON_REQ_USE, and generate different dependencies for pypy-bin |
| 14 |
versus the rest of the python implementations. Or maybe redesign the |
| 15 |
way we handle that entirely. |
| 16 |
|
| 17 |
In any case, pypy-bin was added to the tree without any thought as to |
| 18 |
how to implement the eclass changes, so I have removed it and reverted |
| 19 |
the changes to package.use.force. |
Archives