Add nightly for experimental Konversation Qt Quick branch

Authored by hein on Sep 2 2017, 5:45 AM.



I'd like to add Konversation's wip/qtquick branch to the Flatpak
repo for collaboration with designers.

This is my attempt at a recipe. I'm not sure if this is an
appropriate way to do it. I also don't know if conflicting
files are an issue, or how Discover would handle the two
packages co-existing considering they have the same .desktop
file and appstream data.

Hoping for feedback.

Diff Detail

R256 Flatpak packaging for KDE Applications
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.
hein created this revision.Sep 2 2017, 5:45 AM
hein added a comment.Sep 2 2017, 5:46 AM

Note: I need a debugfull build because the --nui CLI arg (that bypasses the single-instance application mechanic and allows running multiple Konversation instances) is only available in debug builds.

hein updated this revision to Diff 19078.Sep 2 2017, 5:51 AM

From I'm not 100% sure
the top-level branch applies to the git module source, so specify
for good measure.

hein updated this revision to Diff 19079.Sep 2 2017, 5:56 AM

Add Kirigami master ala Klimbgrades' recipe.

apol accepted this revision.Sep 4 2017, 11:09 AM

Yes, default branch is master.

This revision is now accepted and ready to land.Sep 4 2017, 11:09 AM
hein added a comment.Sep 4 2017, 11:11 AM

Should I add it to top-level then instead of todo/? Does anything else need to be done after or will it start generating packages and putting them into the repo at next run?

apol requested changes to this revision.Sep 4 2017, 11:16 AM

Put it in the root, todo/ stuff isn't built, it's for things that don't build.

This revision now requires changes to proceed.Sep 4 2017, 11:16 AM
This revision was automatically updated to reflect the committed changes.
hein added a comment.Sep 5 2017, 7:33 AM

Both this and org.kde.klimbgrades are currently failing because they pull in Kirigami master which needs KF5 5.38. How should we proceed to fix this?