| Commit message (Collapse) | Author | Age |
|
|
|
| |
Until https://github.com/NixOS/nixpkgs/pull/76861 or so is merged
|
|
|
|
|
|
|
|
|
| |
This reverts commit eec83d41e3e7d9ad5bc1086198d972d55bab1203.
This broke hydra evaluation because with this commit submodule values
are allowed to be paths, however the certmgr module uses `either
(submodule ...) path` in its type, meaning it already used paths for
something else which would now be interpreted as a submodule.
|
|\
| |
| | |
Module system improvements for NixOS as a submodule
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This has the beneficial side effect of allowing paths to be used as modules in
types.{submodule,submoduleWith}
|
| | |
|
| |
| |
| |
| | |
Because why not
|
| |
| |
| |
| | |
This will be useful for doing more complicated module evaluations
|
|\ \ |
|
| | |
| | |
| | |
| | | |
js-ghcjs didn't fit in an existing categor.
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |\
| | |
| | | |
Initial implementation of vc4 cross-compile
|
| | | |
|
| |\| |
|
| | |\ |
|
| | | |\
| | | | |
| | | | | |
lib.systems: handle mips family properly
|
| | | | | |
|
| | | | | |
|
| | | |/ |
|
| | | |\
| | | | |
| | | | | |
lib.makeOverridable: Propagate function arguments
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Rename ff to result because that's what it is
- Better indentation
- Less parens
- Comment what overrideWith does
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Apparently nobody ever needed this
- We already have enough ways to override things
- Using overrideDerivation is discouraged
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows querying function arguments of things like fetchFromGitHub:
nix-repl> lib.functionArgs pkgs.fetchFromGitHub
{ fetchSubmodules = true; githubBase = true; ... }
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows querying the arguments you can .override:
nix-repl> lib.functionArgs pkgs.hello.override
{ fetchurl = false; stdenv = false; }
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
And call it overrideArgs in the let binding because that's what it does
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`pipe` is a useful operator for creating pipelines of functions.
It works around the usual problem of e.g. string operations becoming
deeply nested functions.
In principle, there are four different ways this function could be
written:
pipe val [ f1 .. fn ]
pipe val [ fn .. f1 ]
compose [ f1 .. fn ] val
compose [ fn .. f1 ] val
The third and fourth form mirror composition of functions, they would
be the same as e.g. `(f1 << f2 << f3 .. << fn) val`.
However, it is not clear which direction the list should have (as one
can see in the second form, which is the most absurd.
In order not to confuse users, we decide for the most “intuitive”
form, which mirrors the way unix pipes work (thus the name `pipe`).
The flow of data goes from left to right.
Co-Authored-By: Silvan Mosberger <infinisil@icloud.com>
|
| | | |\ \
| | | | | |
| | | | | | |
lib.mkRemovedOptionModule: Show replacement for option usage too
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously mkRemovedOptionModule would only show the replacement
instructions when the removed option was *defined*. With this change, it
also does so when an option is *used*.
This is essential for options that are only intended to be used such as
`security.acme.directory`, whose replacement instructions would never
trigger without this change because almost everybody only uses the
option and isn't defining it.
|
| | | |\ \ \
| | | | | | |
| | | | | | | |
lib: Add armv7a-linux to doubles.nix
|
| | | |\ \ \ \
| | | | |_|/ /
| | | |/| | | |
mkRemovedOptionModule: assert on removed options
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We don't want to ignore config that can mess up machines. In general
this should always fail evaluation, as you think you are changing
behaviour and don't, which can easily create run-time errors we can
catch early.
|
| | | |\ \ \ \
| | | | |/ / /
| | | |/| | | |
Replace uses of splitString for splitting version strings
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | |/ / / |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Markhor is a spiral horned animal that is on the endangered species list
* https://en.wikipedia.org/wiki/Markhor
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
This platform doesn't have a C compiler, and so relies and the changes
in the previous commit to work.
|
|/ / / / |
|
| |/ /
|/| |
| | |
| | | |
It is needed for the `-municode` flag, supposedly.
|
|/ /
| |
| |
| | |
This is needed for android.
|
|\ \ |
|
| |\ \
| | | |
| | | | |
lib.cleanSourceWith: Allow name to be set, optional filter, doc
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change is API-compatible and hash-compatible with the previous
version.
At first I considered to write a rename function too, but adding
it name to cleanSourceWith was a no-brainer for ease of use. It
turns out that a rename function isn't any more useful than
cleanSourceWith.
To avoid having to write the identity predicate when renaming,
the filter is now optional.
builtins.path is supported since Nix 2.0 which is required by nixpkgs
|
| |/ / |
|
|\| | |
|
| | | |
|