nixpkgs/nixos/doc/manual/configuration/package-mgmt.chapter.md

# Package Management {#sec-package-management}

This section describes how to add additional packages to your system.
NixOS has two distinct styles of package management:

-   *Declarative*, where you declare what packages you want in your
    `configuration.nix`. Every time you run `nixos-rebuild`, NixOS will
    ensure that you get a consistent set of binaries corresponding to
    your specification.

-   *Ad hoc*, where you install, upgrade and uninstall packages via the
    `nix-env` command. This style allows mixing packages from different
    Nixpkgs versions. It's the only choice for non-root users.

```{=include=} sections
declarative-packages.section.md
ad-hoc-packages.section.md
```
nixos: nixos/doc/manual/configuration/package-mgmt.xml to CommonMark 2021-09-08 09:47:38 +02:00			`# Package Management {#sec-package-management}`

			`This section describes how to add additional packages to your system.`
			`NixOS has two distinct styles of package management:`

			`- Declarative, where you declare what packages you want in your`
			`configuration.nix`. Every time you run `nixos-rebuild`, NixOS will
			`ensure that you get a consistent set of binaries corresponding to`
			`your specification.`

			`- Ad hoc, where you install, upgrade and uninstall packages via the`
			`nix-env` command. This style allows mixing packages from different
			`Nixpkgs versions. It's the only choice for non-root users.`

nixos-render-docs: add structural includes, use for manual this adds support for structural includes to nixos-render-docs. structural includes provide a way to denote the (sub)structure of the nixos manual in the markdown source files, very similar to how we used literal docbook blocks before, and are processed by nixos-render-docs without involvement of xml tooling. this will ultimately allow us to emit the nixos manual in other formats as well, e.g. html, without going through docbook at all. alternatives to this source layout were also considered: a parallel structure using e.g. toml files that describe the document tree and links to each part is possible, but much more complicated to implement than the solution chosen here and makes it harder to follow which files have what substructure. it also makes it much harder to include a substructure in the middle of a file. much the same goes for command-line arguments to the converter, only that command-lined arguments are even harder to specify correctly and cannot be reasonably pulled together from many places without involving another layer of tooling. cli arguments would also mean that the manual structure would be fixed in default.nix, which is also not ideal. 2023-02-11 08:48:06 +01:00			```{=include=} sections
			`declarative-packages.section.md`
			`ad-hoc-packages.section.md`
nixos: nixos/doc/manual/configuration/package-mgmt.xml to CommonMark 2021-09-08 09:47:38 +02:00			```