| Commit message (Collapse) | Author | Age |
|
|
|
| |
this isn’t useful any more because the ndk we use no longer supports it.
|
|
|
|
|
|
|
| |
New android ndk (18) now uses clang. We were going through the wrapper
that are provided. This lead to surprising errors when building.
Ideally we could use the llvm linker as well, but this leads to errors
as many packages don’t support the llvm linker.
|
|\
| |
| |
| | |
Hydra nixpkgs: ?compare=1512490
|
| |\
| | |
| | | |
TI MSP430 cross compiling
|
| | | |
|
| | | |
|
| |/
| |
| |
| |
| | |
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Suggested-by: Profpatsch <mail@profpatsch.de>
|
|\| |
|
| | |
|
|\|
| |
| |
| | |
Hydra nixpkgs: ?compare=1508887
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The explicit remove helped to uncover some hidden uses of `optionSet`
in NixOps. However it makes life harder for end-users of NixOps - it will
be impossible to deploy 19.03 systems with old NixOps, but there is no
new release of NixOps with `optionSet` fixes.
Also, "deprecation" process isn't well defined. Even that `optionSet` was
declared "deprecated" for many years, it was never announced. Hence, I
leave "deprecation" announce. Then, 3 releases after announce,
we can announce removal of this feature.
This type has to be removed, not `throw`-ed in runtime, because it makes
some perfectly fine code to fail. For example:
```
$ nix-instantiate --eval -E '(import <nixpkgs/lib>).types' --strict
trace: `types.list` is deprecated; use `types.listOf` instead
error: types.optionSet is deprecated; use types.submodule instead
(use '--show-trace' to show detailed location information)
```
|
| |
| |
| |
| |
| |
| | |
descriptions
For convenience, it's not like not having a description is deadly or something.
|
|\| |
|
| | |
|
| |\
| | |
| | | |
systems: add isCompatible handling
|
| | |
| | |
| | |
| | | |
v8 can run any wasm bytecode
|
| | | |
|
| | |
| | |
| | |
| | | |
https://en.wikipedia.org/wiki/Loris
|
|\ \ \
| | | |
| | | | |
Android and related cross fixes
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
dirvish: init at 1.2.1
|
| | | |
|
|\ \ \
| | | |
| | | | |
lib/modules: Change mkAliasOptionModule to use the priority for the alias
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit changes the `mkAliasOptionModule` function to make sure that
the priority for the aliased option is propagated to the non-aliased
option.
This also affects the `mkRenamedOptionModule` function in a similar
fashion.
This also removes the `mkAliasOptionModuleWithPriority` function, since
its functionality is now subsumed by `mkAliasOptionModule`.
This change was recommended by @nbp:
https://github.com/NixOS/nixpkgs/pull/53397#discussion_r245487432
|
| | | |
| | | |
| | | | |
Adds isAlpha to stdenv.<platform> flags.
|
|\ \ \ \
| | |_|/
| |/| | |
|
| |\ \ \
| | | | |
| | | | | |
all-packages.nix: move defaults to package files
|
| | | | | |
|
|\| | | | |
|
| |\| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Comments on conflicts:
- llvm: d6f401e1 vs. 469ecc70 - docs for 6 and 7 say the default is
to build all targets, so we should be fine
- some pypi hashes: they were equivalent, just base16 vs. base32
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
foldl' + mapAttrs)
|
| | | | |
| | | | |
| | | | |
| | | | | |
mapAttrs)
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This should make the composability of kernel configurations more straigthforward.
- now distinguish freeform options from tristate ones
- will look for a structured config in kernelPatches too
one can now access the structuredConfig from a kernel via linux_test.configfile.structuredConfig
in order to reinject it into another kernel, no need to rewrite the config from scratch
The following merge strategies are used in case of conflict:
-- freeform items must be equal or they conflict (mergeEqualOption)
-- for tristate (y/m/n) entries, I use the mergeAnswer strategy which takes the best available value, "best" being defined by the user (by default "y" > "m" > "n", e.g. if one entry is both marked "y" and "n", "y" wins)
-- if one item is both marked optional/mandatory, mandatory wins (mergeFalseByDefault)
|
| | |/ /
| | | |
| | | | |
This adds the "Wasm" system to platform.uname.system. This is used in CMake infrastructure.
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
(into staging)
|
| | | |
| | | |
| | | |
| | | | |
See https://github.com/NixOS/nixpkgs/pull/51447 for some discussion.
|
| | | | |
|
|\ \ \ \
| | |/ /
| |/| | |
|
| |\ \ \
| | | | |
| | | | | |
lib: implement `setPrio`
|
| | | | |
| | | | |
| | | | |
| | | | | |
For when `hiPrio` and `lowPrio` are not enough.
|
|\| | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
lib/modules: Add function to create option alias that respects priority
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit adds a function `mkAliasOptionModuleWithPriority`. This
function will make an alias to an existing option and copy over the
priority.
This functionality is needed for PRs like #53041. In that case
`nixos-generate-config` added an option to `hardware-configuration.nix`
with `mkDefault`. That option was then changed and an alias created for
the old name.
The end user should be able to set the non-alias option in their
`configuration.nix` and have everything work correctly. Without this
function, the priority for the option won't be copied over correctly
and the end-user will get a message saying they have the same option
set to two different values.
|