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