Skip to content
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

How to set update information wihtout using travis ci #316

Open
carlos22 opened this issue Sep 12, 2018 · 10 comments
Open

How to set update information wihtout using travis ci #316

carlos22 opened this issue Sep 12, 2018 · 10 comments

Comments

@carlos22
Copy link

According to https://github.com/AppImage/AppImageUpdate this tool embeds the update information if you are using travis ci. Is it possible to define an update URI/config without using travis?

@TheAssassin
Copy link
Collaborator

You can't. You could only run appimagetool manually.

You can switch to linuxdeploy and linuxdeploy-plugin-qt however. linuxdeploy's built-in appimage plugin supports $UPDATE_INFORMATION. See https://docs.appimage.org/packaging-guide/from-source/linuxdeploy-user-guide.html# for more information.

@probonopd
Copy link
Owner

Well, you can use linuxdeploy --bundle-non-qt-libs and then run appimagetool -u ... on the AppDir.

@pbek
Copy link
Contributor

pbek commented Dec 18, 2020

@probonopd, what is the updateinformation parameter for? It's passing the information to appimagetool, but you need to create the appimage before you can create a zsync file with zsyncmake, right? 😅

@TheAssassin
Copy link
Collaborator

If you set that parameter, it is passed to appimagetool, and appimagetool will auto-generate such a .zsync file.

@pbek
Copy link
Contributor

pbek commented Dec 19, 2020

If you set that parameter, it is passed to appimagetool, and appimagetool will auto-generate such a .zsync file.

Thank you! Sounds nice. But doesn't the AppImage also contain the url to that zsync file or do I pass that future url with the updateinformation? In that case I would also be able to use the appimage updater with my GitHub Action built AppImage, right?

@probonopd
Copy link
Owner

probonopd commented Dec 19, 2020

The place in which the AppImage holds the URL to the zsync file is the update information:

https://github.com/AppImage/AppImageSpec/blob/master/draft.md#update-information

This information is not stored (again) anywhere else. You need to pass the "future url" in the update information format specified above.

@pbek
Copy link
Contributor

pbek commented Dec 19, 2020

Thank you, @probonopd. I saw there even is https://github.com/AppImage/AppImageSpec/blob/master/draft.md#github-releases. Do you have by any chance a repo with a workflow where you use that?

@TheAssassin
Copy link
Collaborator

Check this repo.

@pbek
Copy link
Contributor

pbek commented Dec 19, 2020

Can't see a github folder in this repo. 😅

@probonopd
Copy link
Owner

This repo is currently using Travis CI. On Travis CI the correct update information gets generated automatically thanks to appimagetool -g (which this tool uses under the hood), but for this to work with GitHub Actions AppImage/AppImageKit#1075 needs to be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants