Skip to content

Commit fb05d9e

Browse files
TARGET_APPIMAGE (#43)
Add TARGET_APPIMAGE to AppImageSpec as suggested by AppImageLauncher --------- Co-authored-by: TheAssassin <[email protected]>
1 parent ce1910e commit fb05d9e

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

draft.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ The AppImage Specification is licensed under [The MIT License](https://github.co
2323
- [Metadata]
2424
+ [AppStream]
2525
+ [Update Information]
26+
- [Runtime]
2627
- [Desktop Integration]
2728

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

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

251+
### Runtime
252+
253+
The AppImage runtime is the program that mounts the filesystem image and executes the payload.
254+
255+
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.
256+
250257
### Desktop integration
251258

252259
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.

0 commit comments

Comments
 (0)