Re: KDE Gear projects with failing CI (master + stable) (11 August 2026)
Nate Graham <[email protected]>
| Newsgroups | gmane.comp.kde.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On 8/12/26 11:42 PM, Volker Krause wrote: > On Wednesday, 12 August 2026 21:36:04 Central European Summer Time Nate Graham > wrote: >> It also breaks nightly Flatpak builds, since there's no nightly Flatpak >> runtime yet. > > How many of those do we really have though, and how many of those actually > need unreleased Frameworks and can't also support the previous release? Somewhere between zero and very few — because without a Flatpak runtime that includes master of Frameworks, apps with Flatpak manifests that want to depend on that is a literal an error condition, not just a bad idea. My point is that we can't even consider making it potentially acceptable for apps to depend on master of Frameworks without a nightly master Flatpak runtime. >> Though if we had that, the app contribution docs for a drive-by >> contributor could be collapsed into "run this flatpak-builder command". >> For the past few months I've been building and testing changes to KDE >> apps by building them as Flatpaks, and it's actually been a really nice >> experience overall. > > Absolutely! Throwing new app contributors needlessly down the kdesrc-build > rabbit hole is not an ideal experience, we can do a lot better. See attached > screenshot as a sneak peek on an Akademy talk demo that'll hopefully work, > pushing this even further :) Sounds exciting! Nate