| 1 |
On 10/14/11 12:39 PM, Brian Harring wrote: |
| 2 |
> On Fri, Oct 14, 2011 at 03:29:19PM -0400, Matt Turner wrote: |
| 3 |
>> On Sat, Oct 1, 2011 at 3:16 PM, "Pawe?? Hajdan, Jr." |
| 4 |
>> <phajdan.jr@g.o> wrote: |
| 5 |
>>> OK, so what are the _blocking_ reasons for no EAPI 4 support in |
| 6 |
>>> python.eclass yet? |
| 7 |
>>> |
| 8 |
>>> I understand you have some complicated patches in flight etc etc, but |
| 9 |
>>> are they _required_ for the eclass not to break with EAPI 4? |
| 10 |
>>> |
| 11 |
>>> My point is that I'd like to use pkg_pretend in packages that use |
| 12 |
>>> python.eclass and I can't (for a long time). Unless there are really |
| 13 |
>>> important reasons like breakages I think we should really make |
| 14 |
>>> python.eclass support EAPI=4. |
| 15 |
>> |
| 16 |
>> Two weeks and no response from python@? |
| 17 |
> |
| 18 |
> You probably should've cc'd them. |
| 19 |
|
| 20 |
CC-ing python@ then (but I expect the developers to follow gentoo-dev |
| 21 |
anyway). |
| 22 |
|
| 23 |
In case of no response, I plan to submit the thing to the council |
| 24 |
agenda. I think the parts of python eclass that I use should work with |
| 25 |
EAPI 4. |
Archives