--nextPart6038016.lOV4Wx5bFT
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"; protected-headers="v1"
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker@kde.org>
To: kde-devel@kde.org
Subject: Re: KDE Gear projects with failing CI (master) (9 April 2024)
Date: Wed, 10 Apr 2024 13:04:47 +0200
Message-ID: <5774042.DvuYhMxLoT@daneel>
MIME-Version: 1.0

On Mittwoch, 10. April 2024 09:21:34 CEST Ben Cooksley wrote:
> On Wed, Apr 10, 2024 at 9:51=E2=80=AFAM Ingo Kl=C3=B6cker <kloecker@kde.o=
rg> wrote:
> > On Dienstag, 9. April 2024 23:26:32 CEST Albert Astals Cid wrote:
> > > ktrip - NEW
> > >=20
> > >  * https://invent.kde.org/utilities/ktrip/-/pipelines/657661
> > > =20
> > >   * craft_android builds fail
> >=20
> > *sigh* Why does kirigami master depend on the not yet released ECM 6.1.=
0?
>=20
> Likely as Kirigami itself is a Framework - that being said, it seems a bit
> weird for the version bumps to be pushed to Frameworks before the release
> has been made public (because Craft cannot use them until they're public.=
=2E.)

I learned that this is the usual procedure for Frameworks. But it highlight=
s=20
why it's a bad idea for applications to depend on the master versions of=20
=46rameworks.

> The real question I have though is why does KTrip depend on Frameworks
> master instead of released Frameworks?
> Depending on Frameworks master is something applications should avoid
> unless it is absolutely necessary.

Exactly. ktrip needs a fix that's not in KF 6.0. Instead of adding a patch =
to=20
Craft I told Craft to use Kirigami master. I shouldn't have done this. Less=
on=20
learned.

Regards,
Ingo

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

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

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZhZyTwAKCRCxb1mVFkdK
ujjPAQD2QJedR4tTOnFnsFFsJzWTFoLa9N9fNg8i1b50ZAACBgD/Vga3ZfPyml+a
ccwFamHFaHQEzjWaIEkobJaImxgkegQ=
=C1cB
-----END PGP SIGNATURE-----

--nextPart6038016.lOV4Wx5bFT--