wxmozilla-0.5.6 was just released. This version is needed because earlier versions don't work with wxpython-2.6.3.2 (in portage, ~x86), see bug #31999, comment #15. Upgrade is either trivial ebuild rename from 0.5.4 to 0.5.6 (with wxpython dependency update to >=2.6.3) or the attached patch can be applied. The patch enables a new wxmozilla feature, building against Firefox (see also bug #89653), in addition to updating the wxpython dependency.
Created attachment 85274 [details, diff] wxmozilla-0.5.6.ebuild.patch Patch to update the ebuild to 0.5.6.
In case it got lost in the description (seeing that this is considered enhancement and not a bug fix by jakub@gentoo.org): versions currently in portage *do not work* with wxpython version in portage.
I've version bumped wxMozilla to 0.5.6. I haven't added the firefox USE flag yet. The problem is it doesn't seem to work fine with Firefox 1.5.0.2 headers (the version i've tested). I did a workaround (appended "-DMOZILLA_INTERNAL_API" to wxMozilla build), but it still fails on wxMozillaBrowser. I've left the ebuild with a few comments, so you guys can see what've tried, if you have any progress or if I've done something stupid, let me know.
Re-assign wrt Bug 73835.
Taking under the wing of the wxwindows herd. Browser USE flaggery to do, and stabilizing probably depends on stabilizing of wxGTK/wxpython-2.6.3.x
in progress
Vaclav, the mozilla team would like firefox-1.5 out of the tree ASAP, as soon as 2.0 is stabilized. As such, i'd like to build wxmozilla against seamonkey, which I see you added support for last month. I was wondering if you would be releasing 0.5.7 soon. If not, I'll make a snapshot of current CVS and add that to the tree, and remove 0.5.4 so we can get wxGTK-2.4 out of the tree as well.
(In reply to comment #7) > Vaclav, the mozilla team would like firefox-1.5 out of the tree ASAP, as soon > as 2.0 is stabilized. As such, i'd like to build wxmozilla against seamonkey, > which I see you added support for last month. Not quite: it crashes when built against Seamonkey (which is why there wasn't a new release yet). > I was wondering if you would be releasing 0.5.7 soon. Yes. Hopefully with fixed Seamonkey build, otherwise it works fine with Portage's FF-2.0. > to the tree, and remove 0.5.4 so we can get wxGTK-2.4 out of the tree as well. I don't follow you here: the latest wxmozilla in the tree is 0.5.6, which doesn't depend on wx-2.4, but works with either 2.4 or 2.6, so you can remove 0.5.{3,4} already..
(In reply to comment #8) > > I was wondering if you would be releasing 0.5.7 soon. > > Yes. Hopefully with fixed Seamonkey build, otherwise it works fine with > Portage's FF-2.0. I just noticed the NEWS file after i sent the mail. ;) Cool, i'm testing it now. > I don't follow you here: the latest wxmozilla in the tree is 0.5.6, which > doesn't depend on wx-2.4, but works with either 2.4 or 2.6, so you can remove > 0.5.{3,4} already.. Done.
wxmozilla-0.5.7_pre20070102 is in the tree package.mask'ed now, forced to build against firefox. when 0.5.7 is released it'll default to seamonkey with a firefox USE flag. please test and let me know if i can unmask it.
Closing this as fixed, as Ryan unmasked 0.5.7_pre and removed 0.5.6 to allow mozilla suite to be removed from the tree. We'll remember to put seamonkey support back once it's fixed and 0.5.7 is out, thanks to the commented out DEPENDs in the ebuild for seamonkey
