| Commit message (Collapse) | Author | Age |
|\
| |
| | |
lib.fixedPoints: fix rendering of docs for `extends`
|
| | |
|
|\ \
| |/
|/| |
`lib`: Remove unneeded polyfills
|
| |
| |
| |
| | |
Nix 2.3 (the minimum version needed to evaluate Nixpkgs) supports these, so no need to keep them around.
|
| |
| |
| |
| | |
Nix 2.3 (the minimum version needed to evaluate Nixpkgs) supports these, so no need to keep them around.
|
| |
| |
| |
| | |
Nix 2.3 (the minimum version needed to evaluate Nixpkgs) supports these, so no need to keep them around.
|
| |
| |
| |
| | |
Nix 2.3 (the minimum version needed to evaluate Nixpkgs) supports these, so no need to keep them around.
|
| |
| |
| |
| | |
Nix 2.3 (the minimum version needed to evaluate Nixpkgs) supports these, so no need to keep them around.
|
|\ \
| | |
| | | |
lib.fileset: Fix tests on Darwin, more POSIX
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was found when trying to run the fileset tests on Darwin
(https://github.com/NixOS/nix/pull/9546#issuecomment-1967409445), which mysteriously fail on Darwin:
test case at lib/fileset/tests.sh:342 failed: toSource { root = "/nix/store/foobar"; fileset = ./.; } should have errored with this regex pattern:
lib.fileset.toSource: `root` \(/nix/store/foobar\) is a string-like value, but it should be a path instead.
\s*Paths in strings are not supported by `lib.fileset`, use `lib.sources` or derivations instead.
but this was the actual error:
error: lib.fileset.toSource: `root` (/nix/store/foobar) is a string-like value, but it should be a path instead.
Paths in strings are not supported by `lib.fileset`, use `lib.sources` or derivations instead.
After dissecting this, I find out that apparently \s works on Linux, but not on Darwin for some reason!
From the bash source code, it looks like <regex.h> with `REG_EXTENDED` is used for all platforms the same,
so there's nothing odd there.
It's almost impossible to know where <regex.h> comes from,
but it looks to be a POSIX thing.
So after digging through the almost impossible to find POSIX specifications
(https://pubs.opengroup.org/onlinepubs/007908799/xbd/re.html#tag_007_003_005),
I can indeed confirm that there's no mention of \s or the like!
_However_, there is a mention of `[[:blank:]]`, so we'll use that instead.
|
|\ \ \
| | | |
| | | | |
lib.meta.availableOn: add example in documentation
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
lib.fileset.toList: init
|
| | | |
|
|\ \ \
| | | |
| | | | |
lib: export attrsets.mergeAttrsList
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
See https://github.com/NixOS/nix/pull/9900
|
|\ \ \
| | | |
| | | | |
lib.modules.doRename: Add doc comments
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I don't think these are rendered yet, but this at least provides
the content.
Follow-up to https://github.com/NixOS/nixpkgs/pull/285612
|
| |/ /
|/| | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
lib.types.unique: Check inner type deeply
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The previous code was optimized for the old uniq behavior, which did not
call merge. That's changed, so the legacy path is not a hot path anymore,
and is not worth any tech debt.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We now reuse the `unique` type, which implements this.
Keeping the duplication around would be bad at this point.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This doesn't change uniq. Why not?
- In NixOS it seems that uniq is only used with
simple types that are fully checked by t.check.
- It exists for much longer and is used more widely.
- I believe we should deprecate it, because unique was
already better.
- unique can be a proving ground.
|
|\ \ \ \
| |_|_|/
|/| | | |
lib/systems/inspect: add `isSparc64`
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is useful to distinguish between SPARC64 and SPARC whatever,
because SPARC64 do support compressed kernels.
|
|\ \ \ \
| |/ / /
|/| | | |
lib: make deprecation warnings consistent
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The deprecation warnings in lib were wildly inconsistent. Different
formulations were used in different places for the same meaning. Some warnings
used builtins.trace instead of lib.warn, which prevents silencing; one even
only had a comment instead. Make everything more uniform.
|
|\ \ \ \
| | |_|/
| |/| | |
lib.modules.doRename: Add condition parameter
|
| |/ /
| | |
| | |
| | |
| | | |
This is to support single-to-multi service migrations, so that the
`to` (e.g. `foos.""`) isn't defined unconditionally. See test cases.
|
|\ \ \
| | | |
| | | | |
treewide: fix parse errors with Nix 2.3 and related problems
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
It is useful that all (or almost all) .nix files in nixpkgs at least
parse since it allows for checking syntax in the repository
programmatically without evaluating anything.
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
This allows for adding new, conditionally set, derivation attributes
to an existing derivation without changing any output paths in the
case where the condition is not met.
|
|\ \ \
| |/ /
|/| | |
lib.fileset.gitTracked: Allow clones of shallow repositories
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only reason shallow clones are not the default in
`builtins.fetchGit` is that `revCount` can't be provided when cloning a
shallow repository. However, `revCount` isn't used or exposed by
`lib.fileset`. Hence, allowing cloning shallow repositories makes
`gitTracked` more general without any drawbacks.
Co-authored-by: Silvan Mosberger <github@infinisil.com>
|
|\ \ \
| |/ /
|/| | |
types.nix: fix nonEmptyListOf
|
| | | |
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
|
|
|
| |
According to the WebAssembly design doc, wasm32 is an ILP32 ABI like
x32, mips64n32, and aarch64_ilp32 (Apple Watch). This commits adds
it to the predicate.
https://github.com/WebAssembly/design/blob/1319968ca53fb5c7e7ea6cc210c7b0ed46566a45/CAndC%2B%2B.md?plain=1#L16
|
|\
| |
| | |
Improve the documentation of `lib.extends` and how it relates to overlays
|
| |
| |
| |
| | |
Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Better names:
- self -> final
- super -> prev
- rattrs -> f
- f -> overlay
- Add documentation to the function arguments
- Add some spacing
|
| | |
|
| |
| |
| |
| | |
The previous one was unnecessarily confusing.
|
|\ \
| | |
| | | |
`lib.callPackageWith`: Use abort again instead of throw and fix evaluation errors caused by it
|