AppImage

From Wikipedia, the free encyclopedia
  (Redirected from .klik)
Jump to: navigation, search
AppImage
App-image-logo.svg
Developer(s) Simon Peter
Initial release 2004; 13 years ago (2004)
Stable release
9 / June 3, 2017; 5 months ago (2017-06-03)
Development status Active
Written in C
Operating system Linux
Type Software download system / package format
License MIT License
Website appimage.org

AppImage is a format for distributing portable software on Linux without needing superuser permissions to install the application.[1] It tries also to allow Linux distribution-agnostic binary software deployment for application developers,[2] also called Upstream packaging. Released first in 2004 under the name klik, it was continuously developed since then, renamed in 2011 to PortableLinuxApps and 2013 to AppImage.

Description[edit]

Objectives[edit]

AppImage strives to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, distro agnosticism, no installation, no root permission, being portable, and keeping the underlying operating system untouched.[3]

Properties[edit]

AppImage does not install the application in the traditional Linux sense by putting its various files in the distro's appropriated places in the file system. Instead, like its predecessors klik and portablelinuxapps, no such installation actually takes place, the AppImage file is just its compressed image; this is mounted with FUSE when it runs.

It uses one file per application, each one is self-contained: it includes all libraries the application depends on that are not already part of the targeted base-system. An AppImage of version 1.0 is an ISO 9660 RR file (which can be optionally zisofs compressed) containing a minimal AppDir and a tiny runtime.[4] (Version 2 may use other file system image formats like SquashFS [5][6]). An AppImage application can be added to a live CD by adding only one file to the live CD.

AppImage files are simpler than installing an application. No extraction tools are needed, nor is it necessary to modify the operating system or user environment. Regular users on the common Linux distributions can download it, make it executable, and run it.

History[edit]

klik[edit]

klik installing an application

AppImage's predecessor klik was designed in 2004 by Simon Peter.[7] The client-side software is GPL licensed. klik integrated with web browsers on the user's computer. Users downloaded and installed software by typing a URL beginning with klik://. This downloaded a klik "recipe" file, which was used to generate the .cmg file. In this way, one recipe could be used to supply packages to a wide variety of platforms, with klik only eight programs could be run at once because of the limitation of mounting compressed images with the Linux kernel, unless FUSE was used. The file was remounted each time the program is run, meaning the user could remove the program by simply deleting the .cmg file. A next version, klik2, was in development; and would natively incorporate the FUSE kernel module, but it never reached past the beta stage.[8] Around 2011, the klik project went dormant and the homepage went offline for some time.[9]

PortableLinuxApps[edit]

Simon Peter started a successor project named PortableLinuxApps with similar goals around that time,[2] the technology was adapted for instance by the "portablelinuxgames.org" repository, which provides hundreds of mostly open-source video games.[10]

AppImage[edit]

Around 2013, the software was renamed again from portableLinuxApps to AppImage; the license became the MIT license. AppImage is the format and AppImageKit is a concrete open source implementation, the development happens in a GitHub repository with latest changes from 2017.[11]

Reception and usage[edit]

Klik was in 2007 the inspiration for Alexander Larsson's glick project, the precursor of Flatpak which was released in 2016.[12]

Linus Torvalds' dive log application Subsurface started to use AppImage around 2015. Subsurface's traditional packaging was changed to a portable, self-contained, distro-agnostic AppImage, as binary software deployment for the Linux users of the various Linux distributions turned out to be problematic.[13][14][15]

MuseScore started in April 2016 to use AppImage builds for software deployment for all Linux flavors.[16]

Krita, a digital painting free and open-source software application, is also deployed using AppImage from version 3.0 in May 2016.[17][18]

digiKam, an open source photo management application, also includes an AppImage bundle from version 5.3.0, released in November 2016.[19]

Network World's Bryan Lunduke noted on March 31, 2017 positively the Linux distribution-agnostic packaging of OpenShot with AppImage.[20]

Jaxx distributes the linux version of it's flagship app, a bitcoin wallet, using AppImage.

See also[edit]

References[edit]

  1. ^ Mobily, Tony (2006-04-07). "Free Software Magazine interview with Simon Peter". Free Software Magazine. 
  2. ^ a b Peter, Simon (2010). "AppImageKit Documentation 1.0" (pdf). PortableLinuxApps.org. pp. 2–3. Retrieved 2011-07-29. The AppImage format has been created with specific objectives in mind: Be Simple [...], Maintain binary compatibility [...], Be distribution-agnostic [...], Remove the need for installation [...], Allow to put apps anywhere [...], Do not require recompilation [...], Keep base operating system untouched [...], Do not require root [...] 
  3. ^ AppImage: Linux apps that run anywhere on youtube.com by Peter Simon (June 2016)
  4. ^ [1]
  5. ^ https://github.com/AppImage/AppImageSpec/blob/master/draft.md#type-2-image-format
  6. ^ http://discourse.appimage.org/t/the-future-of-appimage-type-2-and-new-tools/65/2
  7. ^ "Slashdot - Point-and-klik Linux Software Installation?". slashdot.com. 
  8. ^ Screen capture video of Klik2 on video.google.com (archived)
  9. ^ "klik - Linux Software Download". Archived from the original on 2007-06-26. 
  10. ^ "Portable Games for Linux". 
  11. ^ "AppImageKit". github.com. 
  12. ^ Experiments with run-timeless app bundles by Alex Larsson (2007)
  13. ^ Linus Torvalds (2014-08-29). "Q&A with Linus Torvalds" (video). DebConf 2014 Portland. debian.net. 6:28. Retrieved 2016-05-14. I have seen this first hand with the other project I'm involved with, which is my dive log app. We make binaries for Windows and OSX, we basically don't make binaries for Linux. Why? Because making binaries for Linux desktop applications is a major fucking pain in the ass. 
  14. ^ Torvalds, Linus. "This is just very cool". Google+. I finally got around to play with the "AppImage" version of +Subsurface, and it really does seem to "just work". 
  15. ^ Hohndel, Dirk (2015-11-25). "This is just very cool". Google+. I, as the app maintainer, don't want my app bundled in a distribution anymore. Way to much pain for absolutely zero gain. Whenever I get a bug report my first question is "oh, which version of which distribution? which version of which library? What set of insane patches were applied to those libraries?". No, Windows and Mac get this right. I control the libraries my app runs against. [...] With an AppImage I can give them just that. Something that runs on their computer. 
  16. ^ Weiss, Isaac. "MuseScore 2.0.3 is released". MuseScore.org. MuseScore. Retrieved 2016-04-05. 
  17. ^ "Krita 3.0 Released". Krita.org. Krita. 2016-05-31. 
  18. ^ "Krita Appimage for cats". 
  19. ^ "digiKam 5.3.0 is published". www.digikam.org. Retrieved 2016-12-30. 
  20. ^ Bryan Lunduke (Mar 31, 2017). "Linux video editor OpenShot 2.3 impresses: New tools, fast performance". Network World. Retrieved 2017-04-02. Interestingly, OpenShot is distributed via appimage. That means they provide a single binary that can be run on just about any modern Linux distribution. I personally tested this out on openSUSE Tumbleweed with great success—but it should run just as easily on Debian, Fedora or others. I love this approach to distributing software directly from the developers. 

External links[edit]