Re: Using the daemon’s default settings

[Mark H Weaver]

address@hidden (Ludovic Courtès) writes:

> Mark H Weaver <address@hidden> skribis:
>
>> Does this mean that even if I've configured my daemon to use a different
>> set of substitute-urls, when I run 'guix' as root those settings will be
>> overridden?
>
> Yes.
>
>> That seems suboptimal.
>
> Right.
>
>> We have a similar problem with the values of --cores and --max-jobs
>> passed to guix-daemon being ignored because they are always overridden
>> by our client.
>
> Indeed.
>
>> How can we fix these so that the daemon's settings are used unless the
>> user specifically asks to override them in the client?
>
> If you look at nix-daemon.cc:543, there’s currently no way for a client
> to say “default value.”  The only way for a client to get the daemon’s
> default values is to not call the ‘set-build-options’ RPC at all; it’s
> all or nothing.

Ah, okay.

> I think the way forward would be to add a new RPC, say
> ‘set-build-options2’, that would take a list of key/value pairs, where
> keys are option names.  Options not mentioned in a ‘set-build-options2’
> call would keep their default value.
>
> How does that sound?

Sounds good to me!

    Thanks,
      Mark