On Thu, Aug 17, 2017 at 05:34:02PM -0400, Jeremy Bicha wrote: > > But as I've said already, I don't have a problem with just disabling > > webview before buster if it comes to it. It just seems unhelpful to > > boinc users running testing to do that right now, unless you're actually > > at the point of removing the old webkitgtk from testing. > > Removal of webkitgtk from testing is still a few weeks away.
There's been a bit of progress on the wx+GTK3 front - most notably wx upstream have now fixed all the bugs I spotted in my initial testing with a couple of applications. However, I don't think we're very close to starting a transition to wx+GTK3 at this point, so probably we need to decide what to do with boinc. The options for the short term seem to be: * Remove boinc from testing and break it in unstable (which is clearly not helpful for anyone wanting to use it and running either). * Drop the use of wx webview in boinc, which doesn't render it entirely unusable, but isn't great. * Patch boinc to use wxHtmlWindow instead, which has more simplistic rendering, but is probably OK if there's not Javascript or CSS involved. I've no idea how much work that would be, or if boinc upstream has done any work towards this. * Upload parallel packages of wx+GTK3 for boinc to use. I have started work on packaging, but it needs more work so that parallel installs work properly. I'm also hesitant to take this approach without a firm plan to actually do the transition, as I don't think we have the resources to adequately maintain two sets of wx packages (historically we've tried this, and one set just ended up neglected). > But in my opinion, this is the last package blocking removal of > webkitgtk from Ubuntu 17.10. Removal there is also probably a few > weeks away since many Ubuntu removals happen late in Ubuntu's release > cycle.) I'm sure Ubuntu can make that decision for themselves. Cheers, Olly