On Thu, Apr 28, 2005 at 09:48:40PM +0300, Nerijus Baliunas wrote: > > ...since serious licence problems have been discovered... > > IIRC licence problems were in include/msw/gluwin32, so they > are not used/distributed with wxgtk, no? Or do you also package > wxmsw crosscompiler for Debian? Anyway, you can just remove > these files before packaging.
They taint our source package, though none of the 'official' .debs created actually need it. I've already purged the 2.4 packages that way and have a clean set (otherwise the same) on their way for testing/Sarge. For something shouted in caps this problem is embarrassingly old. > And there were very little changes in wxgtk from 2.6.0 release, > so you could just package current cvs IMHO (and it has an important > fix for not being able to use native gtk2 File dialog from wxPython, > so Robin will probably require it anyway). Yes, this is why I've now acted to get these simply removed. The next upload (RRSN, really), will be 2.6 and not a simple forward compatible step for existing binary apps that are packaged with 2.5 (once again, grmbl, mumbl ;). It is pointless to backport things to 2.5 now when 2.6 is fixing big issues in it still every day. Robin just sealed up a 2.6.0 tag for wxPython, but its no good to us because it would have to depend on the -dev package to not crap out randomly on gnomeprint. I've been rolling test builds off head, and as soon as I get a good (enough) one squirted out, I'll get it in the upload queue. Cheers! Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
