-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Feature Request] Flatpak #243
Comments
Tauri Flatpak distribution/bundling is currently work-in-progress. I may be able to come up with a homebrewed solution but unless Tauri releases an easy way to do it (or someone else wants to tackle this), it won't be high on my priority list. |
upgrading to the v2 RC (its essentially fully stable, just missing some documentation) it is pretty simple. |
Ah yea I came across that a couple days ago, it'll probably be done some time after the v2 move is done |
As part of this, would it be possible to include a custom version of webkit2gtk that includes webrtc support? |
I have no idea, I'm pretty unfamiliar with Flatpak lol |
This may not be possible due to one of the best practice guidelines that flathub proposes.
I think that it would be considered a patch to webkit2gtk. |
The patch would not add or remove functionality, merely enable a function that is already there and possible to enable with a single build time flag. Additionally, flathub is not required to distribute flatpaks and so their rules do not matter at all. One of the main benefits of flatpaks is the ability to statically link all of your dependencies and distribute them in a single file similar to a windows MSI/EXE. Dynamically linking to Flathub "runtimes" is entirely optional. Whether that flatpak is distributed via your personal website, github, or flathub is also up to the developer. |
Since every major Linux distro supports flatpak and it's using like a platform independent package manager. Flatpak version should deserve a release also.
Flathub is remote source for flatpak in general.
Please consider adding flatpak packages to flathub.
The text was updated successfully, but these errors were encountered: