Re: Decommissioning Qt 5 CI

--nextPartVRKjMkAET3WUQCfXgjjWLQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Ingo =?UTF-8?B?S2zDtmNrZXI=?= <[email protected]>
To: [email protected]
Subject: Re: Decommissioning Qt 5 CI
Date: Thu, 30 Jul 2026 17:22:21 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Dienstag, 28. Juli 2026 23:36:20 Mitteleurop=C3=A4ische Sommerzeit Alber=
t Astals=20
Cid wrote:
> El dimarts, 28 de juliol del 2026, a les 13:20:56 (Hora d=E2=80=99estiu d=
=E2=80=99Europa
> central), Nicolas Fella va escriure:
> > That said, we have a number of (Plasma) components that we still build
> > for Qt5 for (external) application compatibility (breeze,
> > plasma-integration, etc). So far we have not made a decision to stop
> > doing that, and I'd rather not lose CI for those. That doesn't mean we
> > need Qt5 CI in the current form. Could we use a distribution image with
> > Qt and the few necessary libraries/frameworks baked in? That would be a
> > much smaller image and easier to maintain than the current suse-qt515
> > image.
>=20
> Does the code of those repos change in qt5 related areas?
>=20
> Trying to understand what we want CI for here:
>  * Potentially new qt5 code builds with old qt5/gcc distros?
>  * Non changing qt5 code builds new gcc/stuff from distros?

Additionally to Albert's questions I don't understand why distros that stil=
l=20
need Qt 5 builds of breeze and plasma-integration cannot simply build the=20
latest released versions that support(ed) Qt 5. Why do they need the latest=
=20
and greatest breeze and plasma-integration for the remaining Qt 5 apps whic=
h=20
probably haven't seen a release in years? Does plasma-integration need to=20
match the version of Plasma?

Regards,
Ingo

--nextPartVRKjMkAET3WUQCfXgjjWLQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCamtsLRsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQsW9ZlRZHSrrtQwD/ZohKBm2eKNvaACV+otpw
pS+7KZWchwLcvA0xaJovKqgA/2hMFDU3TewF3gnHlZwqamAzTJgy7EnlAiO5zDF+
fwUM
=lORO
-----END PGP SIGNATURE-----

--nextPartVRKjMkAET3WUQCfXgjjWLQ--