Appimage/en - Revision history

FuzzyBot: Updating to match new version of source page

2025-10-07T17:17:01Z

Updating to match new version of source page

← Older revision		Revision as of 17:17, 7 October 2025
Line 14:		Line 14:
	=== Packaging ===		=== Packaging ===

	See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as ~~nix~~ build dependencies.		See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as Nix build dependencies.
	Following example is a derivation for the program Quba, which is also distributed as AppImage.		Following example is a derivation for the program Quba, which is also distributed as AppImage.

Line 27:		Line 27:
	version = "1.4.0";		version = "1.4.0";
	pname = "quba";		pname = "quba";
	~~name = "${pname}-${version}";~~

	src = fetchurl {		src = fetchurl {
	url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";		url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";
	hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";		hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";
	};		};

	appimageContents = appimageTools.extractType1 { inherit name src; };		appimageContents = appimageTools.extractType1 { inherit name src; };
	in		in
	appimageTools.~~wrapType1~~ {		appimageTools.wrapType2 rec {
	inherit ~~name~~ src;		inherit pname version src;

	extraInstallCommands = ''		extraInstallCommands = ''
	~~mv $out/bin/${name} $out/bin/${pname}~~
	~~install -m 444 -D ${appimageContents}/${pname}.desktop -t $out/share/applications~~
	substituteInPlace $out/share/applications/${pname}.desktop \		substituteInPlace $out/share/applications/${pname}.desktop \
	--replace-fail 'Exec=AppRun' 'Exec=${~~pname~~}'		--replace-fail 'Exec=AppRun' 'Exec=${meta.mainProgram}'
	~~cp -r ${appimageContents}/usr/share/icons $out/share~~
	'';		'';

	meta = {		meta = {
	description = "Viewer for electronic invoices";		description = "Viewer for electronic invoices";
	homepage = "https://github.com/ZUGFeRD/quba-viewer";		homepage = "https://github.com/ZUGFeRD/quba-viewer";
Line 58:		Line 54:
	}		}
	</syntaxhighlight>		</syntaxhighlight>


	== Configuration ==		== Configuration ==
Line 63:		Line 60:
	=== Register AppImage files as a binary type to binfmt_misc ===		=== Register AppImage files as a binary type to binfmt_misc ===

	You can tell the Linux kernel to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter.		You can tell the [[Linux kernel]] to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter:

	~~Since [https://nixos.org/manual/nixos/stable/release-notes#sec-release-24.05-new-services NixOS 24.05], there is a binfmt option~~:

	<syntaxhighlight lang="nixos">		<syntaxhighlight lang="nixos">
	programs.appimage = {		programs.appimage = {
Line 76:		Line 70:
	This way AppImage files can be invoked directly as if they were normal programs		This way AppImage files can be invoked directly as if they were normal programs

	[[Category:Software~~{{#translation:}}~~]]		[[Category:Software]]

FuzzyBot: Updating to match new version of source page

2024-11-04T08:02:35Z

Updating to match new version of source page

← Older revision		Revision as of 08:02, 4 November 2024
Line 24:		Line 24:
	}:		}:

	~~<!--T:11-->~~
	let		let
	version = "1.4.0";		version = "1.4.0";
Line 30:		Line 29:
	name = "${pname}-${version}";		name = "${pname}-${version}";

	~~<!--T:12-->~~
	src = fetchurl {		src = fetchurl {
	url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";		url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";
Line 36:		Line 34:
	};		};

	~~<!--T:13-->~~
	appimageContents = appimageTools.extractType1 { inherit name src; };		appimageContents = appimageTools.extractType1 { inherit name src; };
	in		in
Line 42:		Line 39:
	inherit name src;		inherit name src;

	~~<!--T:14-->~~
	extraInstallCommands = ''		extraInstallCommands = ''
	mv $out/bin/${name} $out/bin/${pname}		mv $out/bin/${name} $out/bin/${pname}
Line 51:		Line 47:
	'';		'';

	~~<!--T:15-->~~
	meta = {		meta = {
	description = "Viewer for electronic invoices";		description = "Viewer for electronic invoices";

FuzzyBot: Updating to match new version of source page

2024-11-04T07:56:27Z

Updating to match new version of source page

← Older revision		Revision as of 07:56, 4 November 2024
Line 15:		Line 15:

	See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as nix build dependencies.		See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as nix build dependencies.
	Following example is a derivation for the program Quba, which is also distributed as AppImage.<syntaxhighlight lang="nix">		Following example is a derivation for the program Quba, which is also distributed as AppImage.

			<syntaxhighlight lang="nix">
	{		{
	lib,		lib,
Line 22:		Line 24:
	}:		}:

			<!--T:11-->
	let		let
	version = "1.4.0";		version = "1.4.0";
Line 27:		Line 30:
	name = "${pname}-${version}";		name = "${pname}-${version}";

	src = fetchurl {		<!--T:12-->
			src = fetchurl {
	url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";		url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";
	hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";		hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";
	};		};

	appimageContents = appimageTools.extractType1 { inherit name src; };		<!--T:13-->
			appimageContents = appimageTools.extractType1 { inherit name src; };
	in		in
	appimageTools.wrapType1 {		appimageTools.wrapType1 {
	inherit name src;		inherit name src;

	extraInstallCommands = ''		<!--T:14-->
			extraInstallCommands = ''
	mv $out/bin/${name} $out/bin/${pname}		mv $out/bin/${name} $out/bin/${pname}
	install -m 444 -D ${appimageContents}/${pname}.desktop -t $out/share/applications		install -m 444 -D ${appimageContents}/${pname}.desktop -t $out/share/applications
Line 45:		Line 51:
	'';		'';

	meta = {		<!--T:15-->
			meta = {
	description = "Viewer for electronic invoices";		description = "Viewer for electronic invoices";
	homepage = "https://github.com/ZUGFeRD/quba-viewer";		homepage = "https://github.com/ZUGFeRD/quba-viewer";

FuzzyBot: Updating to match new version of source page

2024-08-14T08:24:46Z

Updating to match new version of source page

@@ Line 2: / Line 2: @@
 [https://appimage.org/ AppImage] is a monolithic packaging format for linux applications. It contains all dependencies in one file that is composed of an executable with a tacked on filesystem.
-On most distros, all one has to do is download the <code>.AppImage</code> file, make it executable <code>chmod +x $AppImage</code>, and execute it. This doesn't work in NixOS out of the box though, as AppImage files usually (if not always) depend on certain libraries commonly found on other Linux distributions to exist on certain paths; such as <code>/lib64/ld-linux-x86-64.so.2</code>.
+== Usage ==
-== Running an AppImage file on NixOS ==
+=== Run ===
 <syntaxhighlight lang="shell">
@@ Line 10: / Line 12: @@
 $ appimage-run $AppImageFile
 </syntaxhighlight>
-== Register AppImage files as a binary type to binfmt_misc ==
+let
 You can tell the Linux kernel to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter.
@@ Line 25: / Line 73: @@
 This way AppImage files can be invoked directly as if they were normal programs
 [[Category:Software{{#translation:}}]]

FuzzyBot: Updating to match new version of source page

2024-07-21T06:21:48Z

Updating to match new version of source page

New page

<languages/>
[https://appimage.org/ AppImage] is a monolithic packaging format for linux applications. It contains all dependencies in one file that is composed of an executable with a tacked on filesystem.

On most distros, all one has to do is download the <code>.AppImage</code> file, make it executable <code>chmod +x $AppImage</code>, and execute it. This doesn't work in NixOS out of the box though, as AppImage files usually (if not always) depend on certain libraries commonly found on other Linux distributions to exist on certain paths; such as <code>/lib64/ld-linux-x86-64.so.2</code>.

== Running an AppImage file on NixOS ==

<syntaxhighlight lang="shell">
$ nix-shell -p appimage-run
$ appimage-run $AppImageFile
</syntaxhighlight>

== Register AppImage files as a binary type to binfmt_misc ==

You can tell the Linux kernel to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter.

Since [https://nixos.org/manual/nixos/stable/release-notes#sec-release-24.05-new-services NixOS 24.05], there is a binfmt option:

<syntaxhighlight lang="nixos">
programs.appimage = {
enable = true;
binfmt = true;
};
</syntaxhighlight>

This way AppImage files can be invoked directly as if they were normal programs

== How AppImage files are packaged by NixOS ==

See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as nix build dependencies.

[[Category:Software{{#translation:}}]]