Plans for qt6-webengine - will remain limited architectures?

[Steven Robbins]

On Friday, August 16, 2024 7:33:11 A.M. CDT Andrey Rakhmatullin wrote:
> On Fri, Aug 16, 2024 at 07:14:09AM -0500, Steven Robbins wrote:
> > Hi,
> > 
> > A month ago I switched digikam to build with Qt6.  I targeted experimental
> > at the time but have just uploaded to unstable.  In the process I have
> > discovered that qt6-webengine builds on just four architectures.
> 
> 5.
> 
> Compared to 6 for qtwebengine-opensource-src it's not a big difference so
> I would do the same as when digikam needed the latter?

Fair question.  I had left out some details.  Prior to latest upload, debian 
builds of digikam used Qt5 and the dependency on qtwebengine5-dev was 
conditional on the supported architectures.  That worked because webengine 
support was optional.  The last upload is a new digikam release and uses Qt6 
-- and now webengine is no longer optional.

So it turns out that I cannot use the old strategy.  

> > Since this is a core dependency for digikam, I will need to make the same
> > restriction.  If this is a permanent situation, then I'll just change
> > digikam's control file and be done.
> 
> I don't think we do this explicitly in packages that use webengine.

Well, what I can tell you is that I tried the old strategy of making qt6-
webengine-dev conditional on architectures and found that the digikam 
configuration step errors out if qt6-webengine-dev is not present.

https://buildd.debian.org/status/package.php?p=digikam

If there's an alternative, I'm open to ideas!

Thanks,
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20240816/38a0d91b/attachment.sig>