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
make a flatpak for linux #129
Comments
As a fellow linux user, I would like to point out that TagStudio is still in very early development, and probably shouldn't be packaged for flat quite yet. Updating the flatpak would be an extra chore that isn't nessicary at this stage in TagStudio's development. That being said, I'm not familiar with the flatpak packaging process. As one of flatpak's main purposes is stability, if it could, having it clone from the repo wouldn't make sense. |
you just PR the app to the flathub repo and follow its instructions, having it compatible early on will prevent future forking being blocked due to design decisions now |
I'm not familiar with flatpaks but a cursory glance appears to show that sandboxing is one of the primary goals, and while re-enabling whole system or specific folder file access is possible it would be opening holes in that sandbox. Am I understanding the goal/limitations here properly or are there other details that support this as a distribution channel? |
they use portals to escape sandbox. look at the docs or talk to the devs, they know more |
Oh it's not "just". There can be some difficulties to actually make the app compatible with Flatpak due to the portals, but you are right that it's good to have it early at design stage.
Well, it's not that it disables the whole sandbox, but it just gives the permission to the folder and it's content. Users can either do it manually with Flatseal or the Program can have this specified from start. That being said even though I do use Flatpaks on daily basis and generally don't have any major complains the portability is one of those areas that Flatpak isn't the best (kind of). Running it from USB memory stick is pain compared to .exe on Windows, but it is portable in the sense that you can switch your whole Linux distro while retaining the Flatpak folder and the apps should work. The .AppImage is better fit for portable apps. However It doesn't bundle all the runtimes like the Flatpak does so it may not run on every distro so you need to check it. Packaging the programs, ain't it fun... |
As @Qronikarz pointed out, making a Flatpak is not a trivial matter. As well, it does not make sense for the current infrastructure being a Python application experiencing rapid development, and wide scope changes as things are adjusted for user needs and experience. |
You can feel free to reference my Python QT app if you need help with flathub manifests for packaging. |
https://www.flatpak.org/
flathub.org
it's linux's app sharing website
The text was updated successfully, but these errors were encountered: