-
-
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
Migrating to appimageupdatetool to get delta updates #853
Comments
we can apply the patch the same way we do with the "remove" script, to prevent unprivileged users removing the app |
In that case I think it is easier to turn it into a single line, like this:
and insert it between lines 4 and 5 in the typical AM-updater script for appimages. |
I've found something interesting. I tested adding this to the script, after the
Turns out that when you give relative paths to appimageupdatetool instead of full paths like I was doing before, it deletes the wrong file wtf Testing it with brave.
This left me with a |
Now all that's left is waiting for this PR to get merged. |
The PR has been merged so now we can continue. |
the conversion is already in progress, while you are updating old scripts, the new scripts will adopt the template you created. I am doing the same, at least with my Conty-based AppImages. Thanks for the contribution. I think I can close this issue. |
Since we already have appimageupdatetool in the repo, all that we need to do is use it if available.
I took a look at the update function in the main script, and it actually doesn't know the name of the applications, all it does is look for
AM-updater
scripts in APPSPATH.I think it is simpler to simply insert something that would use appimageupdatetool in
AM-updater
and then exit, like this:I did some testing and it seems to work perfectly, some appimages have broken update info in them so I need to make sure that the script doesn't continue to exit 0 when that happens.
EDIT: It works even when the zsync info is broken as appimageupdatetool does indeed not exit with a zero status when that happens, phew!
The text was updated successfully, but these errors were encountered: