On 02/03/2013 07:54, Ben de Groot wrote: > 1. Get Qt5 ready for inclusion in the tree. This includes writing and > improving ebuilds and eclasses, testing to build those, filing bug reports > on failure, finding fixes for those bugs, reporting problems upstream. We > do development in the "qt" overlay, using git.
If you decide to work on Qt5, my suggestion if for somebody to proxy it on main tree *under package.mask* and shoot me an email. Leveraging the tinderbox will at least allow you to find failure points. Good luck, -- Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/
