-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a Flatpak Package For GTK App #29
base: master
Are you sure you want to change the base?
Conversation
Previously the app used "writeas-gtk" as the app id. This was invalid according to freedesktop specifications. See https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-id-generic for details on what an App ID should be.
Creates a flatpak manifest to build the app. Does not yet build the writeas-cli. Related to T663
These are the directories flatpak can create while building an app. Since they should not be committed, they belong in the gitignore.
Flatpak doesn't support running extra commands, so we need to make the cli build it's own target. This is made optional since the cli doesn't always need to be shipped with the app. Related to T663
This was missed during the consolidation of repositiories. Since the app has different executable names for the different builds, the app_id cannot be used as the "exec" line unconditionally.
This run_target no longer exists.
The current issues:
|
Once we get the last two worked out can we merge this? It will be much easier for me to work on number 1 after that |
In addition: should I look into getting flatpak CI set up, or should I make that a separate task? |
Hm, you should be able to publish -- the
I'd say we address this as a separate task. Please feel free to create that in Phabricator |
Ah, apologies. The xclip issue is the only one that blocks publishing, then.
|
Fixes publishing and copies the post link to the clipboard.
Fixed the publishing issue, will look into the draft issue next. |
Allows for flatpak users to have persistent drafts, and for the bundled cli to access them.
For now I added a sandbox hole to the flatpak. In the future I think we should migrate to using xdg dirs instead of a directory in ~/. Flatpak properly handles that use case by default. |
Required for saving to work within flatpaks. Does not affect non-flatpak usage. Related to T663
I'd say that this is ready now. |
Great, sounds good. How can I test this out? |
There are a few ways:
Or I can send you a flatpak bundle. Which way would you prefer? |
Thanks! I'd like to personally know how everything works, so I'm happy to build everything |
Needed to make sure we can create, read, and write to this directory.
I'm having a tough time getting this working, now it's an error when running the built flatpak with
This was after adding the local repo and installing for my user. @thebaer needed dependencies with flatpak:
@BrainBlasted I couldn't find an easy way to install required dependencies so just kept installing whatever the builder comlained was missing. |
@robjloranger do you have xdg-desktop-portal & xdg-desktop-portal-gtk installed? |
@BrainBlasted tried again today and found another error building:
What version of python is required to build? Also, are there any python modules required to build? |
This isn't a python issue by rather an idea where a dependency requires a new cli flag. Working on updating things. |
Adds a test to validate appdata and fixes a mistake that caused validation failure
This creates a development flatpak package for the desktop app. Includes a rework of the non-elementary version's app ID and a fix for an issue introduced in #28