Skip to content
This repository was archived by the owner on Aug 31, 2025. It is now read-only.

Conversation

hoh
Copy link

@hoh hoh commented Jul 17, 2022

Solution: Add a manifest file for flatpak-builder

This is work in progress from the EuroPython 2022 Sprints in Dublin.

I took some inspiration from the following Flathub GitHub repositories:

Known issues:

  • Mu does not detect device vendor and properties, failing to connect via serial (overriding the code makes it work).

Submission on FlatHub

Once the team is happy with the state of this pull request, the manifest should be submitted to FlatHub, the most popular Flatpak repository, for all users to discover using their favorite Linux distribution.

Integration with Pup

I discussed with @tmontes about integrating this with Pup. It would be nice to have Pup generate the Flatpak manifest and organize related files automatically from a multi-platform project description.

Solution: Add a manifest file for flatpak-builder

Known issues:
- Icon does not display correctly on my KDE desktop
- Mu does not detect device vendor and properties, failing to connect via serial (overriding the code makes it work).
@hoh hoh force-pushed the add-flatpak-support branch from 402eaa4 to 8d9148d Compare July 29, 2022 21:28
@hoh
Copy link
Author

hoh commented Jul 29, 2022

In order to be published on Flathub:

Accessing the network is not allowed during the build process, to download extra files, everything that an app requires must be included within the manifest. There is a community provided set of tools to make this easier for some projects (such as npm) that would traditionally want to access the network.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant