GNU bug report logs - #58903
[PATCH] gnu: nix: Update to 2.11.1.

Previous Next

Full log

View this message in rfc822 format

From: phodina <phodina <at> protonmail.com>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: "58903 <at> debbugs.gnu.org" <58903 <at> debbugs.gnu.org>, "go.wigust <at> gmail.com" <go.wigust <at> gmail.com>, Ludovic Courtès <ludo <at> gnu.org>, "i <at> pengmeiyu.com" <i <at> pengmeiyu.com>
Subject: [bug#58903] Specify the build dir for Nix
Date: Mon, 31 Oct 2022 19:18:29 +0000

[Message part 1 (text/plain, inline)]

Hi Tobias,

thanks for feedback!

> 
> > (build-dir nix-configuration-build-dir ;string
> > (default "/tmp"))
> 
> 
> ‘directory’. Plz, no unnec. abbrev.
> 
> The concept LGTM. Calling it a ‘build directory’ might be editorialising too much. Does Nix use it for anything else?

I've updated the patch so there is no abbreviation. I asked on Nix matrix channel and was told just for derivations. But I'm not expert so take it with grain of salt.

Ludo',
you have a lot insight into the build infrastructure and you also took the concepts from Nix.

What do you think about this approach? It should not be premanently set to block device as you loose throughput and increase latency, but it's neccessary for some derivations as not everybody can have powerful machine at their disposal.

Is there some way to share the approach with guix daemon? If I remeber correctly the derivation is offloaded to nix backend - the contents of `nix` directory (haven't yet had the chance to go through the C code).

I guess the machines behind 'https://ci.guix.gnu.org' have enough resources. Or is there some script that handles large derivations? 

Also this might be interesting problem for embedded devices though offloading is definitely the best approach.

----
Petr

[v2-0001-services-nix-Add-more-configuration-fields.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.