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:
> > I was also wondering what exactl
On 07/06/2017 05:54 PM, tj5527 via nix-dev wrote:
> Following the example
> at http://nixos.org/nix/manual/#chap-writing-nix-expressions to build
> hello package. But `nix-build -A hello` throws error "error: cannot
> auto-call a function that has an argument without a default value
> (‘stdenv’)"
>
On 07/06/2017 07:35 PM, Harmen via nix-dev wrote:
> Does that makes sense? Did I forget a 'name' somewhere?
When you use things like
src = ./.;
the directory gets copied into nix store and the resulting path's name
is based on the name of the directory.
--Vladimir
__
On 07/07/2017 01:46 AM, John Ramsden via nix-dev wrote:
> I was also wondering what exactly the 'nixos-rebuild switch' command's
> '--upgrade' flag does.
It does
$ nix-channel --update nixos
Best see the source if you want details, as it's relatively simple:
https://github.com/NixOS/nixpkgs/blob/m
Just a heads-up that I'm working on getting this to build, if anyone
else is interested: https://github.com/NixOS/nixpkgs/pull/27194
So far, jigsaw / modularization does not seem to have required nearly
as many changes to the nix expression as I would've guessed. :)
__
I'm currently using a checked out version of the channels repository
as my channel. I was previously using the integrated channel and using
'system.autoUpgrade.enable = true'. I assume I can no longer use this
service for upgrades while I'm using git. Is there any way to run auto
upgrades whi
On Thu, Jul 06, 2017 at 06:35:15PM +0200, Harmen via nix-dev wrote:
> Hello all,
> another day, another problem :/
>
> I'm trying to figure out why a build generates different build IDs in
> different
> contexts.
> I have a nix expression and some code. If I copy that from machine A
> to machine
Hello all,
another day, another problem :/
I'm trying to figure out why a build generates different build IDs in different
contexts.
I have a nix expression and some code. If I copy that from machine A
to machine B they both give the same build hash. All's fine there.
If on machine B I run nix-bui
Following the example at
http://nixos.org/nix/manual/#chap-writing-nix-expressions to build hello
package. But `nix-build -A hello` throws error "error: cannot auto-call a
function that has an argument without a default value (‘stdenv’)"
How can I fix this problem?
My nix-build (Nix) is 1.11.11
On Tue, Jul 04, 2017 at 08:10:09PM +, zimbatm wrote:
Thanks for the suggestions.
I took away from this that it's best to not have Nix deal with the checkouts.
For now I'll keep things as separate repos, to keep things easier.
Eventually I would like to go to one pkgs tree for all repos, but
10 matches
Mail list logo
