Hi, On Sat, Jun 17, 2017 at 08:42:16PM +0200, Axel Beckert wrote: > Hi Julien, > > Julien Cristau wrote: > > > And obviously, since "qtwebkit" and "webkit" are both mentioned > > > already, the mentioning of "webkit" does not imply any webkit fork as > > > otherwise "qtwebkit" wouldn't be in there. > > > > OK. I didn't think that list is intended as a list of source > > packages. > > Ah, ok, I read it that way as qtwebkit and khtml are current source > package names. If it's not a list of source packages, then qtwebkit shouldn't be listed either, no? After all, that's a WebKit fork as well. > > It does talk about browser engines instead, I believe on purpose, so it > > doesn't have to be that specific about source package names (which > > wouldn't be much help to most users anyway). Maybe we could make that > > clearer. > > Yes, please. > > Basically this was a question during my talk "What's new in Stretch?" > today after having copied this list from the release notes on one of > my slides. > > The question came from a developer of a webkit-based web browser (Cc'ed). That'd be me ;-) > > Or indeed update it to actual current source packages. > > Then webkit should be removed from the list. I just noticed now that > it's no current source package name anymore. it has been removed from > unstable in 2013. As Axel mentioned earlier, I think QtWebEngine should be added as well as I don't expect Qt to be upgraded during the Stretch release. That's based on Chromium, which is somewhat related to WebKit, but still probably distinct enough. Florian -- https://www.qutebrowser.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
Attachment:
signature.asc
Description: PGP signature