Mart Raudsepp

I finally got around to bumping wxGTK in the tree to 2.6.3.3 with all the changes like migrating completely away from using the wxlib.eclass, fixes for stuff that I considered blockers for considering 2.6.3.2 being a stabling candidate, and so on.

As there seem to be reasons to shorten the 30 day stabling policy a little bit for this one, I would appreciate testing success stories in my leio@g.o mail, and failure stories in bugzilla ASAP

Next stop, wxpython-2.6.3.3. I would say tomorrow, but judging on the date I gave for wxGTK, I will not say one this time.

Oh, and if I were a maintainer of a package that has any version that depends on wxGTK-2.4 left in the portage tree, I would take care of cleaning out old ebuilds and making sure things work against wxGTK-2.6, as next next stop is nuking wxGTK/wxpython-2.4.x out of the tree for a well deserved permanent retirement.