bbhtt
bbhtt
The first one is also how it works currently. The version is extracted from the pattern if it exists.
> Please attach or link a screenrecord showcasing the application on Linux using the Flatpak. It says a screenrecord not a screenshot.
Also upstream seems to not want cargo.lock in vcs a) that can't live in Flathub repo b) we can't accept a forked source
Lockfiles are part of the source code, see the note in https://docs.flathub.org/docs/for-app-authors/requirements#required-files
Is unbuildable offline from the git repo not a reason enough for upstream to include the cargo.lock file in vcs... It's very silly.
> The only thing I needed to provide was a git clone in a particular location and copy a directory. Is this acceptable? Ok, but please keep it separate from...
Do you have any screenshots to see how it works?
> I heavily dislike how this is called org.kde.* given it's not software coming from kde.org That's how extension points work in Flatpak. It's named by the where it is...
> This seems like something flatpak should fix then :D I just remembered that the `org.gtk.Gtk3theme` extension point does not match the ID prefix of the parent runtime. It's defined...
The question is will KDE runtime provide such an extension point for third party developers or shall we go on with this one?