-
Notifications
You must be signed in to change notification settings - Fork 530
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
feat: add flatpak output and GHA build step #5609
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
b13ffc1
to
35059f8
Compare
35059f8
to
fa7a1ae
Compare
fa7a1ae
to
00f48fa
Compare
Hello
It is possible to build the flatpak from source. I have done this on a tauri app before, both v1 and v2. You need to use the flatpak-node-generator for the node dependencies and flatpak-cargo-generator for the rust dependencies. Then you can run the build in offline mode, since the flatpak builder cannot access the internet during build. All of this can also be automated in a workflow. |
Hey thanks for chiming in. I know its possible, but reusing the .deb was much quicker and simpler. I'm curious though, are there any other advantages to building it again separately for flatpak? If you have any links for a tauri v2 flatpak build from scratch I'd love to take a look |
Hmm I believe the biggest advantage would be the applying any flatpak specific patches. I know of one Tauri flatpak that has a patch that disables the tauri updater, since updating is handled by the flatpak package manager. Other than that, it is mostly licensing and reproducability that some people care deeply about. I don't know of any Tauri v2 flatpaks built from source, the one I maintain is still v1 for now. But I have built the dev branch of v2 as a flatpak. |
@Milkfat32 awesome, thanks for sharing. Yeah removing the tauri-updater here would be great for example. |
☕️ Reasoning
🧢 Changes
build:flatpak
root package.json script.deb
output.