remove the misleading warning on using nix-env for split outputs#255947
Merged
fricklerhandwerk merged 1 commit intoNixOS:masterfrom Sep 25, 2023
Merged
remove the misleading warning on using nix-env for split outputs#255947fricklerhandwerk merged 1 commit intoNixOS:masterfrom
nix-env for split outputs#255947fricklerhandwerk merged 1 commit intoNixOS:masterfrom
Conversation
fricklerhandwerk
added
the
8.has: documentation
github-actions
bot
added
6.topic: nixos
fricklerhandwerk
force-pushed
the
doc-outputsToInstall
branch
from
c3fad3a to
2b71d0c
Compare
The text was originally added [0] following an apparently incomplete research on how everything plays together. In fact, Nix propagates `outputs` to the corresponding nested derivations, and there is some messy behavior in Nixpkgs that only seems to propagate `meta.outputsToInstall` in `buildEnv`[1]. This change moves the hints on how to use NixOS specifics to NixOS module documentation (which is hopefully easier to find through search.nixos.org), describes the default behavior in Nixpkgs (updating a the link to the source), and removes the confusing mention of `nix-env`. the last of them should not be there to begin with. we don't want beginners to use `nix-env`, as this is known to run them into trouble eventually. [0]: NixOS#76794 [1]: https://github.com/NixOS/nixpkgs/blob/1774d07242995050d2d8a91cb4da0855eac2e472/pkgs/build-support/buildenv/default.nix#L66
fricklerhandwerk
force-pushed
the
doc-outputsToInstall
branch
from
2b71d0c to
333e358
Compare
ofborg
bot
added
10.rebuild-darwin: 0
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-09-21-documentation-team-meeting-notes-81/33490/1 |
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The text was originally added following an apparently incomplete research on how everything plays together. In fact, Nix propagates
outputsto the corresponding nested derivations, and there is some messy behavior in Nixpkgs that only seems to propagatemeta.outputsToInstallinbuildEnv.This change moves the hints on how to use NixOS specifics to NixOS module documentation (which is hopefully easier to find through search.nixos.org), describes the default behavior in Nixpkgs (updating a the link to the source), and removes the confusing mention of
nix-env.the last of them should not be there to begin with. we don't want beginners to use
nix-env, as this is known to run them into trouble eventually.Related: NixOS/nix#8990