-
Notifications
You must be signed in to change notification settings - Fork 78
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
Generate and upload AppImage #173
Conversation
An AppImage is available for testing at https://github.com/probonopd/merkaartor/releases. |
Hi! First of all, thanks for your contribution. I do like the idea, however I'm reluctant to wget and run some files, automatically. I could probably fix that for the upload script, but I'm not sure how to approach the linuxdeployqt binary. |
Mirror a local copy? |
It crossed my mind, but not in the repository. Is there a stable version of the linuxdeployqt that I could fix and compare a checksum in-repo? That seems to be a good compromise. |
It's being built as we speak. Should show up at https://github.com/probonopd/linuxdeployqt/releases/tag/6 real soon. |
Any progress? |
I'm not actively working on this issue/PR. If somebody wants to make it forward, I suggest the following changes:
Honestly, I'm not really stoked about the tooling for appimage and other tools... |
I'm not really stoked about the fact you don't distribute an AppImage, which while perhaps not standard when @probonopd opened this, now is. Honestly I'd say since 2018 the responsibility has shifted from him to you, and not having an AppImage puts you in the difficult-to-install minority. Just an opinion. |
Fun fact: Yes, that's helloSystem FreeBSD. |
@ctrlcctrlv Neither am I. However, the tooling in this PR insists on running on ubuntu bionic. However, ubuntu bionic does not ship reasonably new packages (and I'm not willing to manage the dependencies manually). I did give other tools a try, including flatpak, but wasn't able to put in enough time to make it work. Maybe something changed, as I didn't look into it recently, so I may give it another go. In the meantime, you can try out the snap package mentioned in #230 . |
When developing software, it is general best practice to develop for the oldest rather than for the newest systems that your users might still use. This being said, tools like appimage-builder and go-appimage |
Hi! After a bunch of experimenting, I ended up using appimage-builder to implement this functionality. It doesn't require ancient system and if it really bundles everything necessary, it should be good. The implementation is in PR #280 , sample AppImage is available if you want to give it a try and provide feedback. |
This PR, when merged, will compile this application on Travis CI upon each
git push
, and upload an AppImage to your GitHub Releases page.Providing an AppImage would have, among others, these advantages:
appimaged
--appimage-extract
parameterHere is an overview of projects that are already distributing upstream-provided, official AppImages.
PLEASE NOTE: For this to work, you need to enable Travis CI for your repository as described here prior to merging this, if you haven't already done so. Also, You need to set up
GITHUB_TOKEN
in Travis CI for this to work; please see https://github.com/probonopd/uploadtool.If you have questions, AppImage developers are on #AppImage on irc.freenode.net.