Appimage/en: Difference between revisions

@@ Line 10: / Line 10: @@
 <syntaxhighlight lang="shell">
 $ nix-shell -p appimage-run
-$ appimage-run $AppImageFile
+$ appimage-run path/to/application.AppImage
 </syntaxhighlight>
+===== Additional Packages =====
+Some appimages still have issues, so you can override for additional pkgs such as
+<syntaxhighlight lang="nix">programs.appimage.enable = true;
+programs.appimage.binfmt = true;
+programs.appimage.package = pkgs.appimage-run.override
+{
+  extraPkgs = pkgs:
+  [
+    pkgs.icu
+    pkgs.libxcrypt-legacy
+    pkgs.python312
+    pkgs.python312Packages.torch
+  ];
+};
+</syntaxhighlight>
 === Packaging ===
@@ Line 61: / Line 80: @@
 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:
 <syntaxhighlight lang="nixos">
 programs.appimage = {
@@ Line 68: / Line 88: @@
 </syntaxhighlight>
-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]]