| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
Unlike HOME, I haven't found any benefit to making this non-writeable
and having to write modules for every program that might want to use
it.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Conflicts:
nixpkgs/nixos/modules/misc/documentation.nix
nixpkgs/pkgs/applications/networking/browsers/firefox/packages.nix
nixpkgs/pkgs/applications/window-managers/sway/default.nix
nixpkgs/pkgs/build-support/rust/build-rust-package/default.nix
nixpkgs/pkgs/development/go-modules/generic/default.nix
nixpkgs/pkgs/development/interpreters/ruby/default.nix
nixpkgs/pkgs/development/interpreters/ruby/patchsets.nix
nixpkgs/pkgs/development/libraries/boehm-gc/7.6.6.nix
nixpkgs/pkgs/development/python-modules/django-mailman3/default.nix
nixpkgs/pkgs/servers/mail/mailman/web.nix
nixpkgs/pkgs/top-level/aliases.nix
nixpkgs/pkgs/top-level/all-packages.nix
nixpkgs/pkgs/top-level/impure.nix
|
| |
|
|
|
|
|
|
|
|
| |
I think when I implemented this I didn't know about tmpfiles.d(5).
Now I do, so let's use that instead.
I don't think the imperativeNix option is necessary any more since the
home directory is created read-only, but if it turns out that
.nix-defexpr and .nix-profile are coming back, I can look into the
best way to solve that then.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the nixlib root is the NIX_PATH root, overlays were in the
NIX_PATH as "nixpkgs-overlays". Nixpkgs imports that by default to
look for overlays. This meant that an arbitrary Nixpkgs tree would
end up trying to use the Nixlib overlays, which wouldn't always work.
It would also mean that derivations built from those trees wouldn't
match the ones other people would try to build, which is undesirable
for working on nixpkgs. I think this is unfortunate behaviour for
anybody working on nixpkgs, and nixpkgs probably shouldn't load
overlays from impurely at all by default, but it is what it is.
Since I can't really change what upstream nixpkgs does here, the best
I can do is change the nixpkgs in nixlib. It will now load overlays
from a sibling "overlays" directory. Renaming the "nixpkgs-overlays"
directory at the nixlib root to "overlays" means that it will be
loaded by default _only_ by the nixpkgs it is colocated with. It also
means that it is still accessible in the NIX_PATH as <overlays>, which
is fine and convenient as long as nothing starts looking at that by
default.
|
| |
|
|
| |
This is required for nix repl.
|
| |
|
|
|
| |
Unstable Nix makes the "Nix 2.0" CLI an experimental feature, but
NixOS still uses it.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This has the added benefit of meaning that derivations that depend on
nix.nixPath no longer have to rebuilt any time anything in nixlib
changes, making rebuilds *much* faster.
|
| | |
|
| |
|