This avoids the need to specify a value for every platform. Upstream
does this since commit 8d5037ed ("meson: always skip
IPC_RMID_DEFERRED_RELEASE check when cross-compiling"). We might as
well keep the known true values for Linux and FreeBSD around to
preserve the small optimization.
This commit was created by a combination of scripts and tools:
- an ast-grep script to prefix things in meta with `lib.`,
- a modified nixf-diagnose / nixf combination to remove unused `with
lib;`, and
- regular nixfmt.
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
In https://github.com/NixOS/nixpkgs/issues/456516
user reported eval fails as:
$ nix build --no-link -f. pkgsCross.mingwW64.cairo
error:
… while calling the 'derivationStrict' builtin
at «nix-internal»/derivation-internal.nix:37:12:
36|
37| strict = derivationStrict drvAttrs;
| ^
38|
… while evaluating derivation 'cairo-x86_64-w64-mingw32-1.18.4'
whose name attribute is located at pkgs/stdenv/generic/make-derivation.nix:544:13
… while evaluating attribute 'mesonFlags' of derivation 'cairo-x86_64-w64-mingw32-1.18.4'
at pkgs/stdenv/generic/make-derivation.nix:824:11:
823| cmakeFlags = makeCMakeFlags attrs;
824| mesonFlags = makeMesonFlags attrs;
| ^
825| }
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: Unknown value for ipc_rmid_deferred_release
The change will not fix `caori` build on `windows`
but at least will report unsupported dependencies.
They are not doing anything right now. This is in preparation for their
complete removal from the tree.
Note: several changes that affect the derivation inputs (e.g. removal of
references to stub paths in build instructions) were left out. They will
be cleaned up the next iteration and will require special care.
Note: this PR is a result of a mix of ugly regex (not AST) based
automation and some manual labor. For reference, the regex automation
part was hacked in: https://github.com/booxter/nix-clean-apple_sdk
Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build a08b3a4d19.tar.gz \
--argstr baseRev 57b193d8dd
result/bin/apply-formatting $NIXPKGS_PATH
In Issue #358284 Victor Engmark reports that some PDF conversions are
failing with "out of memory" errors from `cairo`. ppenguin found the
upstream fix that handles it. Let's pull it in.
Closes: https://github.com/NixOS/nixpkgs/issues/358284
We are migrating packages that meet below requirements:
1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration
The tool is here: https://github.com/Aleksanaa/by-name-migrate.
