Le Sun, Feb 11, 2024 at 02:34:35PM +0100, Rafael Sadowski a écrit :
> On Fri Feb 09, 2024 at 08:02:41PM +0100, Landry Breuil wrote:
> > Le Fri, Feb 09, 2024 at 10:26:18AM +0000, Stuart Henderson a écrit :
> > > On 2024/02/09 10:14, Stuart Henderson wrote:
> > > > Is the "remove qtwebkit" approach because it's causing an actual
> > > > problem, or is it just that it's old? Can we switch to qtwebengine where
> > > > possible but still keep qtwebkit for things where it's still needed
> > > > for certain software to work properly? Rendering local HTML files isn't
> > > > a particularly high security risk.
> > > > 
> > > > Regarding qgis, it seems they _can't_ use qtwebengine:
> > > > https://github.com/qgis/QGIS/issues/49512#issuecomment-1244676849
> > > 
> > > Aha - there is https://github.com/qgis/QGIS/pull/53255 which has
> > > been merged into git master, so this requirement might go away soon.
> > 
> > yes, and https://github.com/qgis/QGIS/pull/55627 starts paving the way
> > for qtwebengine - at some point qgis will switch to qt6 which doesnt
> > have qtwebkit, so qtwebengine support will have to come (as
> > https://github.com/qgis/QGIS/issues/54965 said, with things that might
> > not be possible yet...)
> 
> It is confusing to follow all these PRs as a release note.
> 
> > 
> > but i can readd the dep on qtwebkit if it's here to stay in the
> > portstree a little longer :)
> > 
> 
> I have spoken to Stuart, we will stay with qtwebkit until qgis is ready.
> Can you keep an eye on it?

sure, i'll make sure to switch to qt6 and to qtwebengine as soon as
upstream deems it 'ready' :)