Skip to content

docs(builds): correct where a Nix expression build's nixpkgs comes from #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
imkarrer wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(builds): correct where a Nix expression build's nixpkgs comes from #95

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion concepts/nix-expression-builds.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,11 @@ See the [builds concept](/concepts/builds) page for an overview of the different

Nix expression builds are defined by creating files in the `.flox/pkgs/` directory of a Flox environment. These expressions are written in the Nix language, which is incredibly powerful and results in truly reproducible builds.

The environment that contains the builds doesn't need to have any packages installed because all of the build's dependencies are defined within the expression, but if there are any packages installed then Flox will attempt to produce a build that is compatible with any packages in the "toplevel" [package group](/man/manifest.toml#package-descriptors).
The environment that contains the builds doesn't need to have any packages installed, because all of the build's dependencies are defined within the expression.

The base package set a Nix expression build resolves against comes from the catalog: the current `stable` revision of nixpkgs, or the revision named with [`--stability`](/man/flox-build#options). The environment's own packages don't determine it, so installing or upgrading packages never changes which nixpkgs your expressions build against.

Manifest builds work the other way around — they build inside the environment, against the package set the [lockfile](/concepts/environments#manifestlock) pins. An environment containing both kinds of build therefore builds them against two different package sets, which matters when a Nix expression build and a manifest build are expected to link against the same libraries. `flox build` warns you when the two have diverged; run `flox upgrade` to move the environment's packages to the current revision.

## Defining builds

Expand Down
Loading