[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    KDE Gear Qt 5 deps
From:       Jonathan Riddell <jr () jriddell ! org>
Date:       2023-11-01 10:56:37
Message-ID: CANX=XXObbWfaJQpSRH7JWJFM26XtAe3d5Q_OBKnGad2T5srKWA () mail ! gmail ! com
[Download RAW message or body]

There's a couple libraries that distros need to build both Qt 5 and Qt 6
versions of because they have apps which use both.

libkgapi still needs a Qt 5 version for kio-gdrive and a Qt 6 version for
pim bits.

libkcddb needs a Qt 5 version for k3b and a Qt 6 version for kio-audiocd.

So I propose to make standalone releases of the Qt 5 versions using the
names libkgapi5 and libkcddb5 which distros can pick once when they move
their packaging to Qt 6 bits.

How does that sound?  Are there any more such cases?

Jonathan

[Attachment #3 (text/html)]

<div dir="ltr"><div>There&#39;s a couple libraries that distros need to build both Qt \
5 and Qt 6 versions of because they have apps which use both.    \
</div><div><br></div><div>libkgapi still needs a Qt 5 version for kio-gdrive and a Qt \
6 version for pim bits.</div><div><br></div><div>libkcddb needs a Qt 5 version for \
k3b and a Qt 6 version for kio-audiocd.</div><div><br></div><div>So I propose to make \
standalone releases of the Qt 5 versions using the names libkgapi5 and libkcddb5 \
which distros can pick once when they move their packaging to Qt 6 \
bits.</div><div><br></div><div>How does that sound?   Are there any more such \
cases?</div><div><br></div><div>Jonathan</div><div><br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]