Cool, might have to do some experimenting.
--
John Ramsden
On Fri, Jul 7, 2017, at 08:35 PM, Danylo Hlynskyi wrote:
> I've seen this in a wild
>
> system.autoUpgrade.enable = true;
> system.autoUpgrade.flags = lib.mkForce
> [ "--no-build-output"
>
Thanks that's helpful. In other words if I'm using a checked out git
repository I'm no longer able to use 'system.autoUpgrade'.
--
John Ramsden
On Thu, Jul 6, 2017, at 10:56 PM, Vladimír Čunát wrote:
> On 07/07/2017 01:46 AM, John Ramsden via nix-dev wrote:
&
rypicked a few commits and added them
to the 17.03 channel locally.
--
John Ramsden
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev
Oh I see, that clear things up a bit.
On Wed, May 3, 2017, at 11:50 PM, Marc Weber wrote:
> configuration.nix option nixpkgs.config is what ~/.nixpkgs/config.nix is
> for the user in case you missed it.
>
> Thus:
>
> nixpkgs.config.allowUnfree = true;
> nixpkgs.config.packageOverrides = p: .
On Wed, May 3, 2017, at 10:33 PM, Kamil Chmielewski wrote:
> Hi John,
> you could find my https://github.com/kamilchm/.nixpkgs helpfull.
> I use config.nix to manage user pacakges and dofiles and link them
> into ~ with simple script
> https://github.com/kamilchm/.nixpkgs/blob/master/install.sh> Be
om it
on NixOS, the idea of having all my configuration explicitly written out
in configuration files is part of what I like about Nix.
---
John Ramsden
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev
in the nix pills. but nothing that really explains what it is
used for in detail. Could someone point me where I can find this
information?
--
John Ramsden
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev
