-
Notifications
You must be signed in to change notification settings - Fork 9
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
gimp, inkscape, solvespace, rpcs3, openscad, citra-emu, srain: drop and use flatpak #93
Comments
Since I've already invested the effort in packaging them, I'm pretty averse to dropping these particular packages. Granted, we may be able to remove atk from the repo, but I think having native applications is preferable in almost all circumstances to flatpak. Just my 2 cents. |
Honestly, I thought the same. But considering the bloat that comes from this is insane. |
Personally, its quite a lot of work to remove atk and also patch them for muon as well. |
I don't consider 1 package to be that much bloat. |
packages that rely on a dependency that is only required by it:
are you sure? edit: thought you were referring to the context of this issue. sorry. |
i still really suggest using the flatpak for these ngl.. |
I actually have to agree with @ehawkvu here. Having native packages to me is favorable. Users are obviously free to use flatpak themselves and bypass all the hurdles of building i.e. rust, or chromium if they wish to. |
yeah i have to agree native packages is quite nice |
i know this issue might be trivial compared to #87 , but considering flatpak has many advantages such as sandboxing, less maintenance, less stress on the system, and is easier to manage i don't see why not.
KISS users often use Flatpaks for other big programs such as LibreOffice.
The text was updated successfully, but these errors were encountered: