From Fedora Project Wiki
(Adding usage sec) |
(→Usage: Enclosing <AppImage> with code tags) |
||
| Line 2: | Line 2: | ||
== Usage == | == Usage == | ||
To be run they first need to be marked executable (with <code>chmod +x <AppImage></code>, where <AppImage> is the file name of the AppImage, including its file extension) and then run | To be run they first need to be marked executable (with <code>chmod +x <AppImage></code>, where <code><AppImage></code> is the file name of the AppImage, including its file extension) and then run | ||
with <code>./<AppImage></code>. Either that or clicked/double-clicked in one's file manager. | with <code>./<AppImage></code>. Either that or clicked/double-clicked in one's file manager. | ||
Revision as of 21:52, 14 December 2016
An AppImage is a type of cross-distribution packaging (or bundling) format. It is essentially a self-mounting (using Filesystem in Userspace, or FUSE for short) disk image containing an internal file system for running the application it provides. This internal file system includes all the binaries and libraries required by the application that cannot be reasonably expected to be provided by the base operating system (that is, the Linux system on which the AppImage is being run).
Usage
To be run they first need to be marked executable (with chmod +x <AppImage>, where <AppImage> is the file name of the AppImage, including its file extension) and then run
with ./<AppImage>. Either that or clicked/double-clicked in one's file manager.