| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Since we now distribute the programs.sqlite database with the vuizvui
channel, we can make use of it in programs.command-not-found. We change
the default path used to use the nixpkgs sub directory of the vuizvui
channel (by default it expects a channel named nixos containing the
database).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Besides using the default value from options, I could have just used
mkOptionDefault back then when I was writing this, but fortunately using
the default attribute from the option itself now resulted in an eval
error.
Had I used mkOptionDefault, the value just would have been silently
changed to the default value, since in
https://github.com/NixOS/nixpkgs/pull/63810 the default value now has
priority 1000 instead of 1500 (mkOptionDefault).
So since there is no longer an option default, we now can just set our
binary cache in a singleton list (with priority 100) and be done.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's a bit weird to need to write something like this:
nix-build pkgs -A vuizvui.aszlig.vim
We're already within vuizvui, and the filesystem paths are already
structured in a way so that the above is in pkgs/aszlig/vim, so the need
to add the vuizvui attribute to that seems quite pointless and
unnatural.
I have tested this by evaluating a few machines, tests and packages.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two other occasions where packageOverrides are still in use,
one of them is @sternenseemann's fliewatuet machine and another one is
@devhell's package profile.
I've replaced every other occurence of packageOverrides and replaced it
with overlays and checked the store path hash after evaluation.
The reason why I left @sternenseemann's fliewatuet alone was that for
I wasn't quite sure whether "bluez = pkgs.bluez5" is still needed or
intentional to pin it to version 5. Because if it's not the case the
packageOverrides can just be dropped because bluez is already bluez5 in
upstream <nixpkgs>.
For @devhell's package profile, I did the conversion, but the store path
turned out to be a different one than what it was prior to the change.
I did take a quick look at the requisites of the drv and found that sox
was one of the different paths that led to the change in the final store
path.
This obviously needs to be tested and/or investigated first.
Other than that, the main reason why I'm moving everything to overlays
is that it's the replacement for packageOverrides and also has a better
way to pass through chains of overrides than packageOverrides had.
My guess is that after NixOS 17.09, the old packageOverrides function
will be removed, so let's make sure we're ready for that.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell, @sternenseemann
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes sense to put into the core module here, because we already
have the public key in there as well and if we want to use the binary
cache outside of a channel it's a good idea to provide it here by
default.
Being a default of course also means that users can easily override this
using:
nix.binaryCaches = mkForce [ "something else" ];
I've also removed the redundant setting of that option in all of the
machine configurations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @sternenseemann
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit a93b7583084ff9084d73873d80d8dc428406593c.
The issue isn't completely resolved but most of the packages should have
been fixed that tripped the nondeterministic behaviour, see:
https://ghc.haskell.org/trac/ghc/ticket/4012#comment:232
After having done some tests in the past I didn't stumble on this
problem anymore so far, so let's give it a try.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
The name "profiles" really doesn't match what these modules are for.
Instead they define the very core of Vuizvui and its internal plumbing
and those options are available/enabled to all machines and modules.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
