Skip to content

TARGET_APPIMAGE #43

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jul 13, 2024
Merged

TARGET_APPIMAGE #43

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
518c683
TARGET_APPIMAGE
probonopd Jul 13, 2024
3aa3d06
Fix typo
probonopd Jul 13, 2024
9ff58a4
Update draft.md
probonopd Jul 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions draft.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ The AppImage Specification is licensed under [The MIT License](https://github.co
- [Metadata]
+ [AppStream]
+ [Update Information]
- [Runtime]
- [Desktop Integration]

[Introduction]: #introduction "Introduction"
Expand Down Expand Up @@ -247,6 +248,12 @@ You can visit https://www.pling.com/product/add to register a new product on the

The __bintray-zsync__ transport was there to support [Bintray](https://bintray.com/). It is deprecated.

### Runtime

The AppImage runtime is the program that mounts the filesystem image and executes the payload.

If the AppImage runtime is a static binary, then it **MUST** support the environment variable `TARGET_APPIMAGE`. All runtimes **SHOULD** implement this environment variable. If set to an existing path, then the AppImage Runtime will use the filesystem image from the AppImage at that path for all its operations rather than the filesystem image appended to the runtime binary.

### Desktop integration

The software inside the [AppImage] **MAY** integrate into the desktop environment (e.g., by installing a [.desktop file] into the host system) on the user's behalf. However if it does so, it *SHOULD* ensure to get the explicit permission of the user, e.g., by asking for permission in a GUI window, or by reacting to a command line argument.
Expand Down