Re: Debian, (Py)Qt5 and QtWebKit

2016-01-25 Thread Dmitry Shachnev
My original response was rejected by lists.alioth.debian.org because the domain Qt uses for mailing lists is blacklisted. Re-sending it again with a couple of different links (to the mailing list only, as the CCed people already got it)…

Re: Debian, (Py)Qt5 and QtWebKit

2016-01-25 Thread Kovid Goyal
Realistically speaking, the job of replacing WebKit with WebEngine everywhere it is used is impossible. It would take man years of effort with no reward -- other than causing regressions for end users and bug reports for maintainers. WebEngine is only a direct replacement for WebKit in the most

Re: Debian, (Py)Qt5 and QtWebKit

2016-01-25 Thread Florian Bruhin
* Kovid Goyal [2016-01-25 14:25:01 +0530]: > Realistically speaking, the job of replacing WebKit with WebEngine > everywhere it is used is impossible. It would take man years of effort > with no reward -- other than causing regressions for end users and bug > reports for

Re: Debian, (Py)Qt5 and QtWebKit

2016-01-25 Thread Kovid Goyal
On Mon, Jan 25, 2016 at 10:01:44AM +0100, Florian Bruhin wrote: > * Kovid Goyal [2016-01-25 14:25:01 +0530]: > > Realistically speaking, the job of replacing WebKit with WebEngine > > everywhere it is used is impossible. It would take man years of effort > > with no reward

Re: Debian, (Py)Qt5 and QtWebKit

2016-01-24 Thread Scott Kitterman
On Monday, January 25, 2016 08:12:02 AM Florian Bruhin wrote: > Hey, > > (Cc'ing Kovid/Detlev because I think they'll be impacted by this > as well as the upstreams of Eric/Calibre, Cc'ing Axel Beckert because > I'm working with him for the package mentioned later in this mail) OK, kept them in