| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
Deprecation warnings should not be used in Nixpkgs because they spam
innocent "nix-env -qa" users with (in this case) dozens of messages
that they can't do anything about.
This also reverts commit 2ca883338389b7ab995924a0cab0211993bdf1da.
|
|\
| |
| | |
Make `overridePackages` extend rather than replace existing overrides
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it easy to specify kernel patches:
boot.kernelPatches = [ pkgs.kernelPatches.ubuntu_fan_4_4 ];
To make the `boot.kernelPatches` option possible, this also makes it
easy to extend and/or modify the kernel packages within a linuxPackages
set. For example:
pkgs.linuxPackages.extend (self: super: {
kernel = super.kernel.override {
kernelPatches = super.kernel.kernelPatches ++ [
pkgs.kernelPatches.ubuntu_fan_4_4
];
};
});
Closes #15095
|
| |
|
|
|
| |
See also https://github.com/NixOS/nix/issues/749.
|
|
|
|
|
| |
... to be compatible with https://github.com/NixOS/nix/pull/933
while not breaking compatibility with current nix.
|
| |
|
|
|
|
|
|
| |
This is meant to be used by packages who often re-generate their inputs.
Producing valid JSON is easier than nix, and also garantees it's purity.
|
| |
|
|
|
|
|
| |
These functions used to live in pkgs/development/haskell-modules/default.nix,
but they are generic, really, and should be easily accessible to everyone.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is primarily useful in Nix expressions that are also intended to
be used by nix-shell. It allows saying things like:
buildInputs = [ ... ] ++ (if inNixShell then [ emacs ] else [ ]);
This should not be used in Nixpkgs (since the question of what
constitutes a useful nix-shell environment is very subjective).
|
|
|
|
|
|
|
|
| |
This makes it a bit easier to find out the current Nixpkgs version,
e.g.
$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"14.02.35657.66f51a9"
|
| |
|
|
|