A meta-project which contains all tasks and repositories related to packaging KDE software as Flatpak packages.
Oct 6 2019
+1 good stuff!
Oct 5 2019
The Skrooge Binary Factory jobs have now been regenerated and will use the new configuration going forward.
Jul 21 2019
I'm going to close this since the qt 5.10 branch of the flatpak sdk is now "unmaintained".
Jun 14 2019
May 23 2019
Works for tarballs, good enough.
Mar 17 2019
Not needed anymore
Let's leave this branch die with Qt 5.11. Users should be moving away from it anyway.
5.12 is enough for *me*.
It's qt5.10 branch
Same as 5.9, works for me if you really need it, but I wouldn't be putting new things there.
For which branch is this?
Mar 7 2019
Feb 1 2019
Right, for master and stable (currently "3.2").
Just to be sure, you want to have it built both for master and specific branches?
Jan 30 2019
@apol Thanks, adding another nightly for other branch was my initial though. Can we add this? We would be done then.
And doesn't the nightlies we have now already tackle this?
Yes, Ben summarized what I meant. Thanks. We're not yet there (that is, production-ready flatpack or app store of any kind, with QA and regular contributors). We can't have all of this the day one, we need nighties so would-be contributors who are not developers have the chances to test current software (stable/unstable). Current state is that many contributors (power users) run 1 or 2 years old software so even initial conversation within bugs.kde.org is problematic.
With regards to the Windows Store - the work by myself and Hannah only extends to publishing on the Binary Factory. Validation of a working application, and then publishing as part of a release (on download.kde.org and the Windows Store) would still be up to a maintainer as part of their release work.
Jan 29 2019
With regards to Windows, we do have both unstable nightly builds (which the Binary Factory produces for many projects) along with stable builds (which the Binary Factory also produces).
Jan 27 2019
Thanks Aleix. I'd like to understand: you are not planning it but do you see some rejection by principle or by technical reason?
Bottom line is that for Windows there is no such split and stable software "by KDE" has chance to be shipped.
I'm not planning to offer stable releases of KDE software at the moment. I'd like our software maintainers to take responsibility for the binaries we produce. Flathub seems to be reasonably good infrastructure for that so I suggest using it as users already have the remote installed in their systems.
Jan 26 2019
Reassigning this to the Flatpak project, as there is nothing for Sysadmin to do here.
Jan 24 2019
Jan 7 2019
Dec 11 2018
Dec 9 2018
Could this be the problem?
Aleix, the app I built is a my custom app which absent in any repo.
I tried to push it to my local repo(tutorial-repo) but Discover doesn't see anything there, see the scrinshot.
In the Installed apps, I see it but no metadata there:
I provided AppData xml for my app and it seems picked up at build time, still no result.
you don't have to install app data for flatpak. it's downloaded automatically.
Dec 8 2018
Oct 4 2018
Jun 28 2018
You probably want to keep x11 and wayland.