Appimage/ja: Difference between revisions

From NixOS Wiki
Haruki7049 (talk | contribs)
Created page with "=== パッケージング ==="
FuzzyBot (talk | contribs)
Updating to match new version of source page
Line 21: Line 21:
<div lang="en" dir="ltr" class="mw-content-ltr">
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>
 
<syntaxhighlight lang="nix">
{
{
   lib,
   lib,
Line 27: Line 30:
   fetchurl,
   fetchurl,
}:
}:
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<!--T:11-->
let
let
   version = "1.4.0";
   version = "1.4.0";
   pname = "quba";
   pname = "quba";
   name = "${pname}-${version}";
   name = "${pname}-${version}";
</div>


   <div lang="en" dir="ltr" class="mw-content-ltr">
   <!--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";
     hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";
     hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";
   };
   };
</div>


   <div lang="en" dir="ltr" class="mw-content-ltr">
   <!--T:13-->
appimageContents = appimageTools.extractType1 { inherit name src; };
appimageContents = appimageTools.extractType1 { inherit name src; };
in
in
appimageTools.wrapType1 {
appimageTools.wrapType1 {
   inherit name src;
   inherit name src;
</div>


   <div lang="en" dir="ltr" class="mw-content-ltr">
   <!--T:14-->
extraInstallCommands = ''
extraInstallCommands = ''
     mv $out/bin/${name} $out/bin/${pname}
     mv $out/bin/${name} $out/bin/${pname}
Line 58: Line 57:
     cp -r ${appimageContents}/usr/share/icons $out/share
     cp -r ${appimageContents}/usr/share/icons $out/share
   '';
   '';
</div>


   <div lang="en" dir="ltr" class="mw-content-ltr">
   <!--T:15-->
meta = {
meta = {
     description = "Viewer for electronic invoices";
     description = "Viewer for electronic invoices";
Line 72: Line 70:
}
}
</syntaxhighlight>
</syntaxhighlight>
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<div lang="en" dir="ltr" class="mw-content-ltr">

Revision as of 07:56, 4 November 2024

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.

使い方

実行

ほとんどのLinuxディストリビューションでは、.AppImageファイルをダウンロードし、それを実行可能ファイルchmod +x $AppImageにして実行するだけです。ただし、AppImageファイルは通常(常にではないにしても)ハードコードされたパス内の特定のシステムライブラリに依存するため、NixOSではそのままでは機能しません。

$ nix-shell -p appimage-run
$ appimage-run $AppImageFile

パッケージング

See the 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.

{
  lib,
  appimageTools,
  fetchurl,
}:

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

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

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

  <!--T:14-->
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 \
      --replace-fail 'Exec=AppRun' 'Exec=${pname}'
    cp -r ${appimageContents}/usr/share/icons $out/share
  '';

  <!--T:15-->
meta = {
    description = "Viewer for electronic invoices";
    homepage = "https://github.com/ZUGFeRD/quba-viewer";
    downloadPage = "https://github.com/ZUGFeRD/quba-viewer/releases";
    license = lib.licenses.asl20;
    sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ];
    maintainers = with lib.maintainers; [ onny ];
    platforms = [ "x86_64-linux" ];
  };
}

Configuration

Register AppImage files as a binary type to binfmt_misc

You can tell the Linux kernel to use an interpreter (e.g. appimage-run) when executing certain binary files through the use of 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 appimage-run as interpreter.

Since NixOS 24.05, there is a binfmt option:

programs.appimage = {
  enable = true;
  binfmt = true;
};

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