-
Notifications
You must be signed in to change notification settings - Fork 34
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
request for compiled appimage #4
Comments
Should maybe suggest over at https://github.com/teejee2008/conky-manager as well. |
Requested it there too. |
I don't know what it is, but I did a quick search and I do see some requirement in setting one up: https://github.com/AppImage/AppImageKit/wiki/Creating-AppImages It's unfortunate that you have to gather binaries for different versioning, and by the end you are possibly required to do careful hand-tuning for different systems and versions(and now you end up having to develop for 7 different appimages? and users are having to wade through that too?). It looks similar to creating .deb packages except it's more steps and looks a lot more involved. For that matter I think there's an automated script in this source code that teejee originally wrote to create a .deb out of the build. -it's an unofficial "dirty" package, but the functionality is there. On this note of easy installation, Flatpak might be a more straight-forward easier solution: http://docs.flatpak.org/en/latest/first-build.html Personally, although it's a few steps to get it done, I don't see where building this package with the 3 or 4 commands is even that time consuming to matter: https://github.com/zcot/conky-manager2/blob/add-1.10-support/HOWTOBUILD.md
But maybe someone will come along and want to do this appimage thing. It's very easy to pull a fork in here to go build one, and even send back a pull request for it to be included in this source. Really, the best solution is for the Master's of the Universe(Ubuntu Universe repository maintainers) to package it up as is, and then we can just install it using our preferred install method. |
No. You only need to make one AppImage (for the oldest system that you are targeting, we recommend the oldest still-supported LTS release of Ubuntu which currently is trusty.) From where in the documentation did you get this impression? |
@probonopd I don't know anything about it. I just had done a quick search to even see what appimage is and saw documentation and a link to creating app images wiki(as linked above). That was as far as I looked since it laid out an advanced chain of events, without even reading the first points 3, 4, or 5.. -that was more involved than installing teejee's package. That was as far as I got. Like I said, maybe someone else will want to do it. |
Getting a ready compiled appimage would be really usefull
The text was updated successfully, but these errors were encountered: