[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1057755: Qt WebEngine Security Support In Stable



On Saturday, December 16, 2023 4:10:42 PM MST Adrian Bunk wrote:
> On Sat, Dec 16, 2023 at 01:22:13PM -0700, Soren Stoutner wrote:
> > Bookworm released with qtwebengine-opensource-src 5.15.8+dfsg-1, but
> > 5.15.13+dfsg-1~deb12u1 was later uploaded.
> 
> That's not true, bookworm released with 5.15.13+dfsg-1~deb12u1.

How does stable initially release with an ~deb12u1?

> > At this point, the biggest remaining question is what is the private
> > header
> > that angelfish is using in Qt WebEngine and why?
> >
> >...
> 
> No matter what angelfish does, qtwebview-opensource-src will in any case
> also need a rebuild.

Qt WebView is deprecated upstream.  It was based on the same Apple WebKit 
source that WebViewGTK uses.  It was replaced quite a while ago by Qt 
WebEngine, which is based on Google’s Chromium.  There is no Qt 6 version of 
Qt WebView, so it will go entirely away at that point.

But this brings up an interesting question.  Why are the Qt source packages 
building private-dev binary packages?  There was probably some historical 
reason for doing so, but handling security support in stable would be a lot 
easier if we stopped shipping private headers that other packages can build-
depends on.  Perhaps Dmitry or Patrick could provide some background.

-- 
Soren Stoutner
soren@stoutner.com

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: