-
Notifications
You must be signed in to change notification settings - Fork 284
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
Add AppImage release building #1156
Comments
Are there many libadwaita AppImages already? Whilst I think Pinta would usually be a good candidate for being an AppImage, AppImages have to be built on the oldest stable distribution possible. Focusing on Ubuntu, Pinta would build on Ubuntu 24.04 but not 22.04; any AppImages would be implicitly only supported on 24.04+; and the GTK4 features in use are pretty new, I don't think Pinta 2.2/GTK4 would build on Debian Stable as is. The result would likely be something most people expect to "run anywhere" but that doesn't run in most places. |
I would like appimage too. I don't use flatpaks or snaps because they tend to download gigabytes of extra stuff. Appimages might not be as secure, but they're easier to deal with. |
The Pinta snap is 50MB, when including the Gnome and Core dependencies, it's about 350MB. That's smaller than the Windows installation of Pinta in its entireity (that's about 500MB) and 90% of the dependencies it uses deduplicate with other snaps that need them, there's a truth to the idea Snaps and Flatpaks can be large but it's not applicable in every situation and I'd honestly argue not even applicable to most when the maintainer knows what they're doing. For an AppImage to be made and retain universal compatibility, GTK4 and .NET8 would need backporting to something like Debian 10 or RHEL7, to then have Pinta built on a distribution that's 6 years old with libraries never designed to be compatible with it. Otherwise, it's going to be an AppImage that runs on Ubuntu 24.04+, Fedora 40+, etc. It's not unusable, but it's also absolutely not going to be anything as widely supported as what most people think with JRE, Electron, etc, AppImages. I'm not against AppImage where it makes sense as a technology, but I'm still curious if there's generally any GTK4/Libadwaita AppImages, my expectation is probably not many, but maybe someone's put the effort in. |
I wish an AppImage or install Pinta on Debian from their official repositories. Canonical is contrary to GNU: https://www.gnu.org/philosophy/ubuntu-spyware.en.html |
Well a hypothetical GTK3 AppIkage might work. But a GTK4 AppImage is going to involve back porting software tool chains 6 years and possibly outright reverting patches that have already been submitted. That's the implicit ask here. Remove functionality from users who can use it to give to people who'd rather have nothing than something. It's not a strong argument but I wish you luck with it. |
I agree with @JGCarroll that this doesn't make much sense at the moment with the current dependencies of Pinta's @satonotdead re: packaging Pinta in Debian's official repositories - that should be filed as a request with the Debian packaging team (it's not an upstream issue). Pinta used to be packaged by Debian, but hasn't since Pinta 2.0 because Debian doesn't yet support packaging .NET applications |
any news ? |
Description
It would be very nice to have for the GitHub an AppImage release for Pinta especially for the 2.2 dev build. Apps like Gear Lever make AppImage integration quite easy although the compression algorithm should be considered as I believe AppImageLauncher is not maintained actively and newer AppImages built with
zstd
may fail.FreeCAD AppImage issues
The text was updated successfully, but these errors were encountered: