hluk / hluk/CopyQ

Linux: Embed AppImage update information

Open
#3,688 0 comments 0 reactions 0 assignees View on GitHub
flatpak help wanted
Dominant language
C++
Stars
12.3k
Forks
593
Avg merge
2d 8h
Merged PRs (30d)
9

Description

Request to provide `.zsync` file for AppImage delta updates.
Updating will take less amount of data and time due to downloading only `diff`.

info:
- https://github.com/AppImageCommunity/AppImageUpdate#update-information-overview
- https://github.com/AppImage/AppImageSpec/blob/master/draft.md#update-information
- https://github.com/ivan-hc/AppImage-tips#how-to-add-delta-updates

This is a common standard for updating AppImages.
AppImage having update information would also recognized by other software e.g. [AppImageLauncher](https://github.com/TheAssassin/AppImageLauncher), [AppImageUpdate](https://github.com/AppImageCommunity/AppImageUpdate), [AppManager](https://github.com/kem-a/AppManager), [AM](https://github.com/ivan-hc/AM) etc...

Lots of projects already support updating AppImage e.g: [LibreWolf](https://librewolf.dev/librewolf/bsys6/releases), [KeePassXC](https://github.com/keepassxreboot/keepassxc/releases), [Sigil](https://github.com/Sigil-Ebook/Sigil/releases) etc.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the linked AppImage update-information specifications and the release packaging flow for CopyQ's Linux AppImage. Determine where the distributed AppImage is assembled and how its release artifacts are produced; done means the AppImage includes valid update information and a corresponding .zsync artifact that the referenced update tools can recognize.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
build-system, release
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.