Appimage - Revision history

Smudgebun: Added a period to the last sentence

2026-04-10T12:23:00Z

Added a period to the last sentence

← Older revision		Revision as of 12:23, 10 April 2026
Line 101:		Line 101:
	<translate>		<translate>
	<!--T:7-->		<!--T:7-->
	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.
	</translate>		</translate>

	[[Category:Software]]		[[Category:Software]]

Ardenet: Adjust the position of page translation tags

2026-03-07T17:37:36Z

Adjust the position of page translation tags

← Older revision		Revision as of 17:37, 7 March 2026
Line 10:		Line 10:
	<!--T:3-->		<!--T:3-->
	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 system libraries in hardcoded paths.		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 system libraries in hardcoded paths.
			</translate>

	~~</translate>~~
	<syntaxhighlight lang="shell">		<syntaxhighlight lang="shell">
	$ nix-shell -p appimage-run		$ nix-shell -p appimage-run
	$ appimage-run path/to/application.AppImage		$ appimage-run path/to/application.AppImage
	</syntaxhighlight>		</syntaxhighlight>

	<translate>		<translate>
	===== Additional Packages =====		===== Additional Packages =====
	Some appimages still have issues, so you can override for additional pkgs such as<syntaxhighlight lang="nix">programs.appimage.enable = true;
			Some appimages still have issues, so you can override for additional pkgs such as
			</translate>

			<syntaxhighlight lang="nix">programs.appimage.enable = true;
	programs.appimage.binfmt = true;		programs.appimage.binfmt = true;
	programs.appimage.package = pkgs.appimage-run.override		programs.appimage.package = pkgs.appimage-run.override
Line 29:		Line 34:
	pkgs.python312Packages.torch		pkgs.python312Packages.torch
	];		];
	};</syntaxhighlight>		};
			</syntaxhighlight>

			<translate>
	=== Packaging === <!--T:8-->		=== Packaging === <!--T:8-->

Line 77:		Line 84:

	<translate>		<translate>

	== Configuration == <!--T:16-->		== Configuration == <!--T:16-->

Line 85:		Line 91:
	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:
	</translate>		</translate>

	<syntaxhighlight lang="nixos">		<syntaxhighlight lang="nixos">
	programs.appimage = {		programs.appimage = {
Line 91:		Line 98:
	};		};
	</syntaxhighlight>		</syntaxhighlight>

	<translate>		<translate>

	<!--T:7-->		<!--T:7-->
	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
			</translate>

	~~</translate>~~
	[[Category:Software]]		[[Category:Software]]

Abowen: How to add additional packages

2026-02-24T00:34:04Z

How to add additional packages

@@ Line 17: / Line 17: @@
 </syntaxhighlight>
 <translate>
 === Packaging === <!--T:8-->

Turbotimon: /* Run */ Improve start command py showing path instead of cryptic $AppImageFile

2025-11-14T09:42:45Z

Run: Improve start command py showing path instead of cryptic $AppImageFile

← Older revision		Revision as of 09:42, 14 November 2025
Line 14:		Line 14:
	<syntaxhighlight lang="shell">		<syntaxhighlight lang="shell">
	$ nix-shell -p appimage-run		$ nix-shell -p appimage-run
	$ appimage-run ~~$AppImageFile~~		$ appimage-run path/to/application.AppImage
	</syntaxhighlight>		</syntaxhighlight>
	<translate>		<translate>

Pigs: link to linux kernel

2025-06-01T06:26:53Z

link to linux kernel

← Older revision		Revision as of 06:26, 1 June 2025
Line 69:		Line 69:

	<!--T:5-->		<!--T:5-->
	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:
	</translate>		</translate>
	<syntaxhighlight lang="nixos">		<syntaxhighlight lang="nixos">

FliegendeWurst: fix category

2025-03-09T16:15:45Z

fix category

← Older revision		Revision as of 16:15, 9 March 2025
Line 83:		Line 83:

	</translate>		</translate>
	[[Category:Software~~{{#translation:}}~~]]		[[Category:Software]]

FliegendeWurst: fix example for newer wrapType2

2024-12-30T17:52:43Z

fix example for newer wrapType2

← Older revision		Revision as of 17:52, 30 December 2024
Line 20:		Line 20:

	<!--T:9-->		<!--T:9-->
	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.
	</translate>		</translate>
Line 34:		Line 34:
	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 67:		Line 63:

	<translate>		<translate>

	== Configuration == <!--T:16-->		== Configuration == <!--T:16-->

Mic92: drop 24.05 compat

2024-12-03T08:23:22Z

drop 24.05 compat

← Older revision		Revision as of 08:23, 3 December 2024
Line 72:		Line 72:

	<!--T:5-->		<!--T:5-->
	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:

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

	</translate>		</translate>
	<syntaxhighlight lang="nixos">		<syntaxhighlight lang="nixos">

Haruki7049: Delete comments in code block

2024-11-04T08:02:04Z

Delete comments in code block

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

	~~<!--T:11-->~~
	let		let
	version = "1.4.0";		version = "1.4.0";
Line 37:		Line 36:
	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 43:		Line 41:
	};		};

	~~<!--T:13-->~~
	appimageContents = appimageTools.extractType1 { inherit name src; };		appimageContents = appimageTools.extractType1 { inherit name src; };
	in		in
Line 49:		Line 46:
	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 58:		Line 54:
	'';		'';

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

Haruki7049: Fix to allow translators to ignore code blocks

2024-11-04T07:55:11Z

Fix to allow translators to ignore code blocks

← Older revision		Revision as of 07:55, 4 November 2024
Line 21:		Line 21:
	<!--T:9-->		<!--T:9-->
	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.
			</translate>

			<syntaxhighlight lang="nix">
	{		{
	lib,		lib,
Line 68:		Line 71:
	</syntaxhighlight>		</syntaxhighlight>

			<translate>
	== Configuration == <!--T:16-->		== Configuration == <!--T:16-->