doc/manual: reword 'nixpkgs reference manual' to just 'nixpkgs' manual (#537491)

This commit is contained in:
Johannes Kirschbauer
2026-07-04 16:30:21 +00:00
committed by GitHub
4 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
The `nix-shell` command has popularized the concept of transient shell environments for development or testing purposes.
<!--
We should try to document the product, not its development process in the Nixpkgs reference manual,
We should try to document the product, not its development process in the Nixpkgs manual,
but *something* needs to be said to provide context for this library.
This is the most future proof sentence I could come up with while Nix itself does not yet make use of this.
Relevant is the current status of the devShell attribute "project": https://github.com/NixOS/nix/issues/7501
+1 -1
View File
@@ -1,4 +1,4 @@
# Nixpkgs Reference Manual {#nixpkgs-manual}
# Nixpkgs Manual {#nixpkgs-manual}
## Version @MANUAL_VERSION@
```{=include=} chapters
+1 -1
View File
@@ -29,7 +29,7 @@
"firefox": {},
"webkit": {}
}
needle = re.compile("Nix.*Reference Manual")
needle = re.compile("Nix.* Manual")
if len(sys.argv) != 3 or sys.argv[1] not in browsers.keys():
print(f"usage: {sys.argv[0]} [{'|'.join(browsers.keys())}] <url>")
sys.exit(1)
+1 -1
View File
@@ -72,7 +72,7 @@ rustPlatform.buildRustPackage (finalAttrs: {
Due to `uv`'s (over)eager fetching of dynamically-linked Python executables,
as well as vendoring of dynamically-linked libraries within Python modules distributed via PyPI,
NixOS users can run into issues when managing Python projects.
See the Nixpkgs Reference Manual entry for `uv` for information on how to mitigate these issues:
See the Nixpkgs Manual entry for `uv` for information on how to mitigate these issues:
https://nixos.org/manual/nixpkgs/unstable/#sec-uv.
For building Python projects with `uv` and Nix outside of nixpkgs, check out `uv2nix` at https://github.com/pyproject-nix/uv2nix.