| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | ci/eval: accept `nix` directly•••Previously we were taking nixVersions and this made external use from
the Lix repo's CI annoying.
We should probably also test other nix versions than stable (i.e. also
latest and Lix), but this involves writing GitHub Actions about it and
maybe not running it on every single PR. Future work.
| Jade Lovelace | 2025-06-10 | 1 | -1/+2 |
| * | lib, treewide: introduce `repoRevToName` and use it to cleanup most `fetch*` ... | lassulus | 2025-06-10 | 2 | -1/+103 |
| |\ |
|
| | * | lib, treewide: introduce `repoRevToName`, use it in most `fetch*` functions•••This patch adds `lib.repoRevToName` function that generalizes away most of the
code used for derivation name generation by `fetch*` functions (`fetchzip`,
`fetchFromGitHub`, etc, except those which are delayed until latter commits
for mass-rebuild reasons).
It's first argument controls how the resulting name will look (see below).
Since `lib` has no equivalent of Nixpkgs' `config`, this patch adds
`config.fetchedSourceNameDefault` option to Nixpkgs and then re-exposes
`lib.repoRevToName config.fetchedSourceNameDefault` expression as
`pkgs.repoRevToNameMaybe` which is then used in `fetch*` derivations.
The result is that different values of `config.fetchedSourceNameDefault` now
control how the `src` derivations produced by `fetch*` functions are to be
named, e.g.:
- `fetchedSourceNameDefault = "source"` (the default):
```
$ nix-instantiate -A fuse.src
/nix/store/<hash>-source.drv
```
- `fetchedSourceNameDefault = "versioned"`:
```
$ nix-instantiate -A fuse.src
/nix/store/<hash>-libfuse-2.9.9-source.drv
```
- `fetchedSourceNameDefault = "full"`:
```
$ nix-instantiate -A fuse.src
/nix/store/<hash>-libfuse-2.9.9-github-source.drv
```
See the documentation of `config.fetchedSourceNameDefault` for more info.
| Jan Malakhovski | 2025-05-31 | 2 | -1/+103 |
| * | | lib.mkEnableOption: fix syntax error in example comment | Florent Charpentier | 2025-06-10 | 1 | -2/+2 |
| * | | treewide: fix typos in comments (#413240) | Pol Dellaiera | 2025-06-02 | 4 | -5/+5 |
| |\ \ |
|
| | * | | treewide: fix typos | Peder Bergebakken Sundt | 2025-06-02 | 4 | -5/+5 |
| | |/ |
|
| * | | lib/types: add doc warning to addCheck (#412364) | Johannes Kirschbauer | 2025-06-02 | 1 | -1/+7 |
| |\ \ |
|
| | * | | lib/types: add doc warning to addCheck | Johannes Kirschbauer | 2025-05-30 | 1 | -1/+7 |
| * | | | lib/tests: avoid full rebuild when only maintainers change•••The vast majority of CI jobs to build the lib tests are caused by
changes in the maintainer list. In this case, we currently run the full
test-suite which takes 3-4 minutes. By moving the maintainers and teams
tests out of the test-with-nix file, we save almost all of that.
Building only those two tests on a change is almost instant. This only
works, because we previously enabled cachix for the workflow.
Note, that these tests are not actually run with both nix versions, even
though they were listed in the "test with specific nix version" file.
That's because we only differ in the nix version run *inside* the
sandbox, but not doing the outer build.
Since this file seems to be re-used by NixOS/nix' CI, this is
technically a small loss in coverage for that repo, but nixpkgs CI
considerations outweigh that. But because of this, I left the other
non-nix-version-specific tests in that file.
| Wolfgang Walther | 2025-06-02 | 3 | -10/+11 |
| | |/
|/| |
|
| * | | lib.systems: don't throw if go unsupported•••Better to have a value that can actually be checked for, rather than
throwing, so optional Go support can be disabled when unsupported.
| Alyssa Ross | 2025-05-30 | 1 | -1/+1 |
| |/ |
|
| * | lib: prefer replaceString over replaceStrings | Gutyina Gergő | 2025-05-28 | 3 | -5/+5 |
| * | lib/strings: init replaceString | Gutyina Gergő | 2025-05-28 | 3 | -0/+47 |
| * | lib.systems.loongarch64-multiplatform: init (#402689) | Philip Taron | 2025-05-27 | 1 | -0/+11 |
| |\ |
|
| | * | lib.systems.loongarch64-multiplatform: init | Weijia Wang | 2025-05-25 | 1 | -0/+11 |
| * | | lib.fileset.difference: fix type docs | Wolfgang Walther | 2025-05-26 | 1 | -1/+1 |
| |/ |
|
| * | Revert "lib.meta.availableOn: Return false if pkg parameter is null"•••I believe this change is wrong both theoretically and practically.
Theoretically, `null` is available on every platform, because
`buildInputs = [ null ];` always succeeds and never throws a platform
availability error. `null` should be handled consistently with packages
that have no explicit list of supported platforms, as it of course
has no such list itself.
Practically, we use `null` to represent libraries that are always
present on a platform and do not require a library (for instance,
because they are part of `libc` or the macOS SDK). This has been
used for a long time by `libintl` (on all non‐glibc platforms),
and is also now used by `libGL` and friends on Darwin. This change
broke the check SDL3 does for OpenGL availability on Darwin, causing
<https://github.com/NixOS/nixpkgs/issues/407056>, which had to be
worked around by <https://github.com/NixOS/nixpkgs/pull/409525>.
Both `libintl` and `libGL` should count as available on platforms
where their functionality is part of the standard build environment,
and a package that is completely unavailable and whose functionality
cannot be expected should not use `null`, as it should result in
errors if used in a dependency list on an unsupported platform.
I accept that overriding with `null` is often a useful way to disable
dependencies that don’t have explicit feature flags, but I do not
think that making it work better with feature flags conditioned on
availability is worth the inconsistency and problems caused by this
change. Packages can instead expose the relevant feature flags as
arguments that default to the `lib.meta.availableOn` check or, if they
want to keep an “override the dependency to `null`” interface,
insert an explicit `pkg != null && …` check.
Additionally, the pull request was merged over a week after all
breaking changes were restricted for the 25.05 release. I believe that
the potential problems of dealing with the effects of this change for
an entire release cycle – the first release cycle where `libGL` is
`null` on Darwin, a change I made before the deadline and before this
change to `lib.meta.availableOn` – offset the risks of backporting
this revert at such a late stage.
It will cause overrides to backwards‐incompatibly revert to the
behaviour they had before the change, but since such overrides were
not possible until a few weeks ago, I hope that is an acceptable risk
compared to the potential issues leaving this in the release can
cause, given that it was merged after the deadline and has already
broken an existing construction in Nixpkgs.
This reverts commit 9338d924dbe0c6b93daec3bf435322812fd176fe.
| Emily | 2025-05-23 | 1 | -2/+1 |
| * | lib.systems: raise minimum loongarch64 feature support (#403201) | Aleksana | 2025-05-23 | 3 | -1/+69 |
| |\ |
|
| | * | lib.systems.examples: separate loongarch64 for desktop and embedded variants | aleksana | 2025-05-22 | 2 | -1/+24 |
| | * | lib.systems.architectures: add loongarch64 | aleksana | 2025-05-22 | 1 | -0/+45 |
| * | | lib.systems.elaborate.canExecute: handle different gcc.arch (#403549) | Aleksana | 2025-05-23 | 2 | -1/+79 |
| |\ \
| |/
|/| |
|
| | * | lib.systems.elaborate.canExecute: handle different gcc.arch | aleksana | 2025-05-22 | 1 | -1/+15 |
| | * | lib.systems.architectures: add hasInferior and canExecute function | aleksana | 2025-05-22 | 1 | -0/+64 |
| * | | treewide: maintainers-list.nix -> maintainer-list.nix (#409585) | Simon Hollingshead | 2025-05-22 | 1 | -1/+1 |
| * | | lib.strings: init toCamelCase (#402372) | Johannes Kirschbauer | 2025-05-18 | 3 | -0/+80 |
| |\ \ |
|
| | * | | lib.strings: init toCamelCase | Heitor Augusto | 2025-05-11 | 3 | -0/+80 |
| * | | | lib/.version: Fix version file formatting | Sigmanificient | 2025-05-16 | 1 | -1/+1 |
| * | | | 25.11 is Xantusia25.11-pre | Leona Maroni | 2025-05-16 | 2 | -2/+2 |
| * | | | nixos/image/repart: Use own assertions / warnings. (#406940) | Arian van Putten | 2025-05-15 | 1 | -0/+68 |
| |\ \ \ |
|
| | * | | | lib/asserts: Factor out NixOS's toplevel assertion / warning logic. | Will Fancher | 2025-05-14 | 1 | -0/+68 |
| * | | | | ipxe: correct licensing information (#390934) | Aleksana | 2025-05-15 | 1 | -0/+5 |
| |\ \ \ \ |
|
| | * | | | | licenses: add gpl2UBDLPlus•••Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
| Fernando Rodrigues | 2025-05-13 | 1 | -0/+5 |
| | |/ / / |
|
| * | | | | lib.systems.examples.riscv64-musl: init | Alyssa Ross | 2025-05-15 | 1 | -0/+4 |
| * | | | | lib/systems: remove android cruft (#406682) | Morgan Jones | 2025-05-14 | 1 | -15/+3 |
| |\ \ \ \ |
|
| | * | | | | lib/systems: remove android cruft•••These used legacy names for Android SDK and NDK versions, so now we can
do away with them.
| Morgan Jones | 2025-05-12 | 1 | -15/+3 |
| | |/ / / |
|
| * / / / | docs: fix typo: `readDir` -> `dirOf`•••The example code here uses `dirOf`, not `readDir`. I assume this was
just a silly typo.
| Jeremy Fleischman | 2025-05-12 | 1 | -1/+1 |
| |/ / / |
|
| * | | | lib.modules.importApply: Fix doc typo; `_key` → `key`•••The `importApply` docs reference using the `_key` attr along with
`importApply` or `_file`, however the actual attr name used by the
module system is `key`.
| Matt Sturgeon | 2025-05-08 | 1 | -1/+1 |
| * | | | lib: refactor lib.attrsets.{mapAttrs', mapAttrsToList} and mapAttrs'' in the ... | Johannes Kirschbauer | 2025-05-08 | 1 | -2/+2 |
| |\ \ \ |
|
| | * | | | lib: refactor lib.attrsets.{mapAttrs', mapAttrsToList} and mapAttrs'' in the ...•••The new implementation of `mapAttrsToList` is simpler than the previous one, avoiding an extra string conversion. Benchmarking shows a slight performance improvement. See the discussion here: https://discourse.nixos.org/t/another-implementation-of-mapattrstolist
Additionally, I searched nixpkgs for expressions equivalent to the old `mapAttrsToList` and replaced them with direct calls to the new implementation.
| ccicnce113424 | 2025-05-08 | 1 | -2/+2 |
| | | |/
| |/| |
|
| * | | | .editorconfig: move subfolder config into separate .editorconfig files•••This avoids paths in the top-level file getting out-of-sync, because the
.editorconfig files would be moved together with the files they target.
| Wolfgang Walther | 2025-05-07 | 1 | -0/+3 |
| * | | | Merge master into staging-next | Vladimír Čunát | 2025-05-04 | 1 | -0/+29 |
| |\ \ \ |
|
| | * \ \ | lib.systems: add golang platform dialect (#403030) | Jörg Thalheim | 2025-05-04 | 1 | -0/+29 |
| | |\ \ \ |
|
| | | * | | | lib.systems: add golang platform dialect | aleksana | 2025-04-30 | 1 | -0/+29 |
| | | |/ / |
|
| * | | | | Merge master into staging-next | nixpkgs-ci[bot] | 2025-05-02 | 1 | -1/+2 |
| |\| | | |
|
| | * | | | lib.meta.availableOn: Return false if pkg parameter is null•••To fix overriding packages that checks for platform compatibility, like pipewire.
`pipewire` contains the following logic to enable support for ldac depending on library platform compatibility:
```nix
ldacbtSupport = lib.meta.availableOn stdenv.hostPlatform ldacbt
```
Which is used later in the expression to create a Meson flag:
```nix
(lib.mesonEnable "bluez5-codec-ldac" (bluezSupport && ldacbtSupport))
```
This means that attempting to build `pipewire` without `ldacbt` like:
```nix
pipewire.override {
ldacbt = null;
}
```
will fail because the the Meson flag indicates the feature should be enabled, but the library is passed to `buildInputs` as `null`.
| adisbladis | 2025-05-02 | 1 | -1/+2 |
| | |/ / |
|
| * | | | Merge remote-tracking branch 'origin/master' into staging-next | K900 | 2025-04-30 | 1 | -0/+5 |
| |\| | |
|
| | * | | lib.systems.inspect.patterns.isEfi: add loongarch | aleksana | 2025-04-29 | 1 | -0/+5 |
| | |/ |
|
| * | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-04-24 | 3 | -7/+1 |
| |\| |
|
| | * | Revert "pkgs/top-level/stage.nix: add pkgsLLVMLibc"•••This reverts commit 41b14024d24bd7488b58d7a252f8f16b194d57f9.
| zowoq | 2025-04-24 | 3 | -7/+1 |
| * | | font-{alias,util}, gccmakedep, libp{ciacces,threadstub}s: refactor and migrat... | jopejoe1 | 2025-04-24 | 1 | -0/+20 |
| |\ \
| |/
|/| |
|
| | * | font-util: refactored, moved to pkgs/by-name and renamed from xorg.fontutil | Zitrone | 2025-04-22 | 1 | -0/+15 |
