| 1 |
On 10/14/2011 5:28 PM, Matt Turner wrote: |
| 2 |
> On Fri, Oct 14, 2011 at 5:25 PM, Matthew Summers |
| 3 |
> <quantumsummers@g.o> wrote: |
| 4 |
>> Its being worked on currently. There are many fairly difficult issues |
| 5 |
>> to be worked through here. |
| 6 |
> |
| 7 |
> That's kind of the question though. What's are the issues? |
| 8 |
|
| 9 |
The only issue that has been raised is that the eclass will die if |
| 10 |
python_pkg_setup is not called from the ebuild. This can happen either |
| 11 |
implicitly (the function is exported) or explicitly (by calling it from |
| 12 |
pkg_setup). |
| 13 |
|
| 14 |
I haven't gotten a very good explanation as to why this is necessary |
| 15 |
from Arfrever. He has given some very short, non-informative |
| 16 |
explanations like "Jython requires it". |
| 17 |
|
| 18 |
Puzzling it out myself takes quite a bit of brain power, given the |
| 19 |
complexity of the eclass. There may in fact be no reason for it at all. |
| 20 |
Either way, somebody needs to actually understand it. |
| 21 |
|
| 22 |
Other than that issue, I think we really just need to do some testing. |
| 23 |
Despite there being a large number of people in the python herd, there |
| 24 |
aren't many who actually have the time to do this. |
| 25 |
|
| 26 |
It would be helpful if folks could brain storm a list of python related |
| 27 |
packages to test under EAPI 4. I may have some time over the next few |
| 28 |
weekends to work on this. |
Archives