Nix (package manager)/zh: Difference between revisions

Mayer (talk | contribs)
Created page with "Nix包管理器"
Tags: Mobile edit Mobile web edit
 
Ardenet (talk | contribs)
No edit summary
Tags: Mobile edit Mobile web edit
 
(83 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<div lang="en" dir="ltr" class="mw-content-ltr">
<languages/>
Nix is a package manager and build system that parses reproducible build instructions specified in the [[Nix Expression Language]], a pure functional language with lazy evaluation. Nix expressions are pure functions<ref>Values cannot change during computation. Functions always produce the same output if their input does not change. </ref>taking dependencies as arguments and producing a ''[[Derivations|derivation]]'' specifying a reproducible build environment for the package. Nix stores the results of the build in unique addresses specified by a hash of the complete dependency tree, creating an immutable package store (aka the [[#Nix store|nix store]]) that allows for atomic upgrades, rollbacks and concurrent installation of different versions of a package, essentially eliminating [https://en.wikipedia.org/wiki/Dependency_hell dependency hell].
{{Navbox Nix}}
</div>
{{Disambiguation|message=本文介绍的是 Nix 包管理器。不要与 [[Nix ecosystem|Nix 生态系统]][[Nix (language)|Nix 语言]] [[Nix (command)|Nix 命令]] 混淆。}}


<div lang="en" dir="ltr" class="mw-content-ltr">
Nix 是一个软件包管理器和构建系统,它解析由 [[Nix (language)|Nix 表达式语言]] (惰性求值的纯函数式语言) 指定的可复现的构建指令。Nix 表达式是纯函数<ref>值在计算过程中不会改变。当函数的输入不变时,函数总是输出相同的结果。</ref>,它接受依赖作为参数,并生成一个 ''[[Derivations|derivation]]'',用于指定该软件包的可复现的构建环境。Nix 把构建结果存储在由完整依赖树的哈希值指定的唯一地址中,从而创建了一个不可变的包存储 (即 [[#Nix store|nix store]]),使得原子升级、回滚、以及同时安装同一软件包的不同版本成为可能,从根本上消除了 [[Wikipedia:Dependency hell|依赖地狱]]。
== Usage ==
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Usage"></span>
=== Installation ===
== 用法 ==
NixOS: Nix is being installed while you install NixOS.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Installation"></span>
If you intend to utilize Nix on a different Linux distribution or a Mac computer, you can perform a standalone installation:  The [https://nixos.org/manual/nix/stable/installation/installation installation section of the Nix manual] describes the installation of standalone Nix from binary or source.
=== 安装 ===
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
在 [[NixOS|NixOS]] 上,Nix 已经自动安装好了。
=== Nix commands ===
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
如果您想在其他 Linux 发行版或在 macOS 上使用, 您可以按照 [https://nix.dev/manual/nix/stable/installation/ Nix 手册的安装章节] 来安装 Nix。
The [[Nix command|Nix commands]] are documented in the [https://nixos.org/manual/nix/stable/command-ref/command-ref Nix reference manual]: main commands, utilities and experimental commands. Prior to version 2.0 (released in February 2018) there have been different commands.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Nix_commands"></span>
=== Configuration ===
=== Nix 命令 ===
On NixOS, Nix is configured through the [https://search.nixos.org/options?query=nix. <code>nix</code> option].
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
[[Nix (command line utilities)|Nix 命令]] 在 [https://nix.dev/manual/nix/stable/command-ref/ Nix 参考手册] 中有详细记录:主要命令、工具命令和实验性命令。在 2.0 版本(于 2018 年 2 月发布)之前,命令有所不同。
Standalone Nix is configured through <code>nix.conf</code> (usually found in <code>/etc/nix/</code>), which defines a number of settings relating to evaluation, builds, garbage collection, sandboxing, and user permissions. Details on the available options are [https://nixos.org/manual/nix/stable/command-ref/conf-file found in the Nix reference manual].
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Configuration"></span>
Even further configuration is possible with [[Home Manager]] to manage declarative environments for a single user. For system-wide configuration on Linux, you can use [https://github.com/numtide/system-manager System Manager]. For system-wide configuration on macOS, [https://github.com/LnL7/nix-darwin nix-darwin] is the preferred solution.
=== 配置 ===
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
在 NixOS 上, Nix 可以通过 [https://search.nixos.org/options?query=nix <code>nix</code> 选项] 进行配置。
== Internals ==
 
</div>
独立安装的 Nix 通过 <code>nix.conf</code> 进行配置(其通常位于 <code>/etc/nix/</code>)。可用选项的详细说明可在 [https://nix.dev/manual/nix/stable/command-ref/conf-file Nix 参考手册] 中找到.
 
你也可以使用 [[Home Manager|Home Manager]] 配置 Nix,它为单用户提供管理声明式环境的能力。对于系统范围的配置,可以在 Linux 上使用 [https://github.com/numtide/system-manager System Manager],在 macOS 上使用 [https://github.com/nix-darwin/nix-darwin nix-darwin]。
 
<span id="Internals"></span>
== 内部机制 ==


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


<div lang="en" dir="ltr" class="mw-content-ltr">
{{Split|reason=Nix store 在概念上有足够的独立性,值得单独成文。}}
Packages built by Nix are placed in the read-only ''Nix store'', normally found in <code>/nix/store</code>. Each package is given a unique address specified by a cryptographic hash followed by the package name and version, for example <code>/nix/store/nawl092prjblbhvv16kxxbk6j9gkgcqm-git-2.14.1</code>. These prefixes hash all the inputs to the build process, including the source files, the full dependency tree, compiler flags, etc. This allows Nix to simultaneously install different versions of the same package, and even different builds of the same version, for example variants built with different compilers. When adding, removing or updating a package, nothing is removed from the store; instead, symlinks to these packages are added, removed or changed in ''profiles''.
 
</div>
Nix 构建的软件包会被放置在只读的 ''Nix store'' 中,通常位于 <code>/nix/store</code>。每个软件包都会被赋予一个唯一的地址,该地址由加密哈希值、软件包名称和版本组成,例如 <code>/nix/store/nawl092prjblbhvv16kxxbk6j9gkgcqm-git-2.14.1</code>。这些前缀对构建过程中的所有输入进行哈希,包括源文件、完整的依赖树、编译器参数等。这使得 Nix 能够同时安装同一软件包的不同版本,甚至是同一版本的不同构建(例如使用不同编译器构建的变体)。在添加、移除或更新软件包时,存储中的内容不会被删除;相反,''profiles'' 中指向这些软件包的符号链接会被添加、移除或更改。
 
<span id="Cleaning_the_Nix_store"></span>
==== 清理 Nix store ====
 
有关清理 Nix store 的信息,请参阅 {{NixOS Manual|name=NixOS 手册:章节 - 清理 Nix 存储|anchor=#sec-nix-gc}}。
 
<span id="Nix_store_corruption"></span>
==== Nix store 损坏 ====
 
有关修复 Nix store 损坏的信息,请参阅 {{NixOS Manual|name=NixOS 手册:章节 - Nix store 损坏|anchor=#sec-nix-store-corruption}}。
 
<span id="Valid_Nix_store_names"></span>
==== 有效的 Nix store 名称 ====
 
{{main|Valid Nix store path names}}


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


<div lang="en" dir="ltr" class="mw-content-ltr">
为了构建一个连续的用户或系统环境,Nix 会将 Nix 存储库中的条目软链接到 ''配置(profiles)'' 中。这些配置文件是 Nix 实现回滚的前端:由于存储库是不可变的,并且会保留配置文件的先前版本,因此恢复到之前的状态只需更改指向先前配置文件的符号链接即可。更准确地说,Nix 会将二进制文件软链接到 Nix 存储库中代表用户环境的条目。这些用户环境随后会被软链接到存储在 <code>/nix/var/nix/profiles</code> 目录下的带标签的配置文件中,而这些配置文件又会被软链接到用户的 <code>~/.nix-profile</code> 文件。
In order to construct a coherent user or system environment, Nix symlinks entries of the Nix store into ''profiles''. These are the front-end by which Nix allows rollbacks: since the store is immutable and previous versions of profiles are kept, reverting to an earlier state is simply a matter of change the symlink to a previous profile. To be more precise, Nix symlinks binaries into entries of the Nix store representing the user environments. These user environments are then symlinked into labeled profiles stored in <code>/nix/var/nix/profiles</code>, which are in turn symlinked to the user's <code>~/.nix-profile</code>.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Sandboxing"></span>
=== Sandboxing ===
=== 沙盒 ===
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
启用沙盒构建后,Nix 将为每个构建过程设置一个隔离环境。这用于移除构建环境中的的其它隐藏依赖项,以提高构建结果的可复现性。这包括在构建过程中对 <code>fetch*</code> 函数之外的网络访问,以及对 Nix Store 之外的文件访问的不可行。根据操作系统的不同,对其他资源的访问也会被阻止(例如,在 Linux 上,进程间通信也是被隔离的)。
When sandbox builds are enabled, Nix will setup an isolated environment for each build process. It is used to remove further hidden dependencies set by the build environment to improve reproducibility. This includes access to the network during the build outside of <code>fetch*</code> functions and files outside the Nix store.  Depending on the operating system access to other resources are blocked as well (ex. inter process communication is isolated on Linux); see [https://nixos.org/nix/manual/#sec-conf-file nix.conf section] in the Nix manual for details.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Linux 系统默认启用沙盒,而 macOS 系统则默认禁用沙盒。
Sandboxing is enabled by default on Linux, and disabled by default on macOS.
[https://github.com/NixOS/nixpkgs/ Nixpkgs] 的拉取请求中,提交者被要求启用沙盒进行构建测试(请参阅拉取请求模板中的 <code>Tested using sandboxing</code>),因为 [https://nixos.org/hydra/ 官方 Hydra 构建] 中也使用了沙盒。
In pull requests for [https://github.com/NixOS/nixpkgs/ Nixpkgs] people are asked to test builds with sandboxing enabled (see <code>Tested using sandboxing</code> in the pull request template) because in [https://nixos.org/hydra/ official Hydra builds] sandboxing is also used.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
要为 Nix 配置沙盒,请在 <code>/etc/nix/nix.conf</code> 中设置 <code>sandbox = true</code>;要为 NixOS 配置沙盒,请在 <code>configuration.nix</code> 中设置 <code>nix.useSandbox = true;</code>。自 NixOS 17.09 起,<code>nix.useSandbox</code> 选项默认为 <code>true</code>
To configure Nix for sandboxing, set <code>sandbox = true</code> in <code>/etc/nix/nix.conf</code>; to configure NixOS for sandboxing set <code>nix.useSandbox = true;</code> in <code>configuration.nix</code>. The <code>nix.useSandbox</code> option is <code>true</code> by default since NixOS 17.09.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Alternative_Interpreters"></span>
=== Alternative Interpreters ===
=== 可选的解释器 ===
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
目前正在进行一项计划,从零开始使用 Rust 重新实现 Nix
There is an ongoing effort to reimplement Nix, from the ground up, in Rust.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://code.tvl.fyi/tree/tvix tvix]
* [https://cs.tvl.fyi/depot/-/tree/tvix tvix]
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Nix 2.18 还有一个名为 Lix 的社区分支,专注于正确性、易用性和可扩展性。虽然它也把 Nix 的一些组件移植到了 Rust,但它不像 Tvix 那样是从零开始重写的。
There is also a community-led fork of Nix 2.18 named Lix, focused on correctness, usability, and growth. While it has also ported some components of Nix to Rust, it is not a ground-up rewrite like Tvix.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://lix.systems/ lix]
* [https://lix.systems/ lix]
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
早期尝试可以在 [https://riir-nix.github.io/ riir-nix] 中找到。
Earlier attempts can be found on [https://riir-nix.github.io/ riir-nix]
 
</div>
<span id="Notes"></span>
== 备注 ==


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


<div lang="en" dir="ltr" class="mw-content-ltr">
[[Category:Pedias]]
[[Category:Pedias]]
[[Category:Nix]]
[[Category:Nix]]
[[Category:Incomplete]]
[[Category:Incomplete]]
[[Category:Software]]
[[Category:Software]]
</div>