forked from LnL7/nix
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'obsidian/better-exe-lookup' into meson-…
…functional-tests
- Loading branch information
Showing
164 changed files
with
1,452 additions
and
594 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,11 @@ | ||
add_project_arguments( | ||
'-Wno-deprecated-declarations', | ||
'-Wimplicit-fallthrough', | ||
'-Wdeprecated-copy', | ||
'-Werror=suggest-override', | ||
'-Werror=switch', | ||
'-Werror=switch-enum', | ||
'-Werror=unused-result', | ||
'-Wdeprecated-copy', | ||
'-Wignored-qualifiers', | ||
# Enable assertions in libstdc++ by default. Harmless on libc++. Benchmarked | ||
# at ~1% overhead in `nix search`. | ||
# | ||
'-Wimplicit-fallthrough', | ||
'-Wno-deprecated-declarations', | ||
language : 'cpp', | ||
) |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
synopsis: The "build-hook" setting" default is less useful when using `libnixstore` as a library | ||
prs: | ||
- 11178 | ||
--- | ||
|
||
*This is an obscure issue just affecting uses of `libnixstore` the library outside of the Nix executable.* | ||
|
||
As part the ongoing [rewrite of the build system](https://github.com/NixOS/nix/issues/2503) to use [Meson](https://mesonbuild.com/), we are also switching to packaging individual Nix components separately (and building them in separate derivations). | ||
This means that when building `libnixstore` we do not know where the Nix binaries will be installed --- `libnixstore` doesn't know about downstream consumers like the Nix binaries at all. | ||
This has a small adverse affect on remote building --- the `build-remote` executable that is specified from the `build-hook` setting will not be gotten from the (presumed) installation location, but instead looked up on the `PATH`. | ||
This means that other applications linking `libnixstore` that wish to use remote building must arrange for the `nix` command to be on the PATH (or manually overriding the setting) in order for that to work. | ||
|
||
Long term we don't envision this being a downside, because we plan to [get rid of `build-remote` and the build hook setting entirely](https://github.com/NixOS/nix/issues/1221). | ||
There is simply no need to add a second layer of remote-procedure-calling when we want to connect to a remote builder. | ||
When the build hook protocol did in principle support custom ways of remote building, that can also be accomplished with a customer service for the ssh or daemon/ssh-ng protocols, or with a custom store class. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
--- | ||
synopsis: "Add `pipe-operators` experimental feature" | ||
prs: | ||
- 11131 | ||
--- | ||
|
||
This is a draft implementation of [RFC 0148](https://github.com/NixOS/rfcs/pull/148). | ||
|
||
The `pipe-operators` experimental feature adds [`<|` and `|>` operators][pipe operators] to the Nix language. | ||
*a* `|>` *b* is equivalent to the function application *b* *a*, and | ||
*a* `<|` *b* is equivalent to the function application *a* *b*. | ||
|
||
For example: | ||
|
||
``` | ||
nix-repl> 1 |> builtins.add 2 |> builtins.mul 3 | ||
9 | ||
nix-repl> builtins.add 1 <| builtins.mul 2 <| 3 | ||
7 | ||
``` | ||
|
||
`<|` and `|>` are right and left associative, respectively, and have lower precedence than any other operator. | ||
These properties may change in future releases. | ||
|
||
See [the RFC](https://github.com/NixOS/rfcs/pull/148) for more examples and rationale. | ||
|
||
[pipe operators]: @docroot@/language/operators.md#pipe-operators |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
synopsis: "Improve handling of tarballs that don't consist of a single top-level directory" | ||
prs: | ||
- 11195 | ||
--- | ||
|
||
In previous Nix releases, the tarball fetcher (used by `builtins.fetchTarball`) erroneously merged top-level directories into a single directory, and silently discarded top-level files that are not directories. This is no longer the case. The new behaviour is that *only* if the tarball consists of a single directory, the top-level path component of the files in the tarball is removed (similar to `tar`'s `--strip-components=1`). | ||
|
||
Author: [**Eelco Dolstra (@edolstra)**](https://github.com/edolstra) |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.