This is a qemu based nixos test that attempts to cover configuration
resembling real linux-builder-vz disk layout. The test validates that
store path referred in kernel cmdline survive gc as well as reboot.
(It was actually broken for this builder before recent fixes.)
Assisted-by: Codex, gpt-5.6-sol medium
This function replaces `apple-sdk.sourceRelease`. It is not
SDK-specific, but going forward the source releases will be updated
together, build with their associated SDK, and rely on cc-wrapper’s
support for enforcing availability annotations to ensure they still
build and run on all supported versions of macOS.
These were added in <https://github.com/NixOS/nixpkgs/pull/109626> in
2021, and used to provide the definition of `sudo`. That was reverted
shortly after, in <https://github.com/NixOS/nixpkgs/pull/112006>.
While embedding these paths in the output of a derivation is
potentially legitimate, using them as build inputs to other
derivations is not so much; they won’t work in the sandbox, and
using `sudo(8)` in a build especially doesn’t seem like a great
idea. Using `/usr/bin/ditto` directly along with `sandboxProfile` or
`__impureHostDeps` is a better mechanism than a wrapper package if
a build really needs `ditto(1)`.
Adds the headers and text-based stubs for the system libc++.
This package is using the newest available version (currently 15.5)
because libc++ uses static availability checks to prevent using features
not supported by older deployment targets.
Co-authored-by: Emily <vcs@emily.moe>
Picking up where #414321 left off, we can now simplify some things by
using `pkgs.libc` or `targetPackages.libc` consistently.
Individual packages should probably continue using `stdenv.cc.libc`, for
now at least, since it is possible they are given a `stdenv.cc` with an
alternative libc, but for the treewide code, the top-level `libc`
package is preferable and easier to work with.
Co-authored-by: Tristan Ross <rosscomputerguy@protonmail.com>
Broken since at least 24.11, stuck on a version from 2018, and no
longer relevant with the new SDK pattern. A newer version is packaged
separately for the Swift compiler, so maybe it could be revived there
if people clamour for a source‐built CoreFoundation in the future.
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 b32a094368
result/bin/apply-formatting $NIXPKGS_PATH
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 78e9caf153
result/bin/apply-formatting $NIXPKGS_PATH
