On Thu, 2013-02-14 at 20:21 +0100, Josselin Mouette wrote: > Hi guys, > > I’ve been looking at the Mono.Webbrowser class problem in Debian, and > this looks pretty bad to me.
It's pretty much fucked for the Wheezy timescale. > * Gluezilla doesn’t look like a workable solution. Nah, Mozilla aggressively broke their embeddability some time after Firefox 3.6. It isn't going to start working again. Another browser engine is the only option. > * Someone can package mono-webbrowser which contains the Webkit > backend, but the repository contains only 3 commits, the last of > which was 3 years ago, so it doesn’t look like a long-term > solution. It doesn't quite work. It opens a whole new can of worms relating to binding a GTK3 version of Webkit and broken behaviour in gobject-introspection with frameworks like Mono. There's only one person working on it, and she only works on it when I bully her about it on Twitter so she donates her free time to the cause - the fix would be a stack of NEW and a whole lot of work I can't expect from a lone volunteer. > * We can make the library raise a warning or exception when > someone tries to use the class. Huh, so currently it just crashes. I thought it just rendered a white control - I guess that was the behaviour when gluezilla is installed but no workable version of Firefox is found. Would an "empty control" workaround suffice for Wheezy? > * We can entirely remove the two packages, although I’m not sure > what the consequence is for Winforms applications. Make them all uninstallable. > Could you enlighten us or, even better, upload a workaround for this bug > to wheezy? If I come up with any bright ideas, sure. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
