Subject: Re: bug#20217: Allow users to use the daemon's default settings

From: [email-masked] (Ludovic Courtès)
Date: Sun, 15 Jan 2017 15:57:13 +0100

[email-masked] (Ludovic Courtès) skribis:

> [email-masked] (Ludovic Courtès) skribis:
>
>> Mark H Weaver <[email-masked]> skribis:
>>
>>> Ludovic Courtès <[email-masked]> writes:
>>>
>>>> commit 4d58122071bbd7bb56c9658a9bbe7621bf3e423d
>>>> Author: Ludovic Courtès <[email-masked]>
>>>> Date:   Sun Mar 22 23:43:25 2015 +0100
>>>>
>>>>     store: Default to a non-empty list of substituters.
>>>>     
>>>>     Fixes <http://bugs.gnu.org/20163>.
>>>>     Reported by Mark H Weaver <[email-masked]>.
>>>>     
>>>>     * guix/store.scm (%default-substitute-urls): New variable.
>>>>       (set-build-options): Change default value of #:substitute-urls to
>>>>       %DEFAULT-SUBSTITUTE-URLS.
>>
>> [...]
>>
>>> 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.
>
> This particular issue of substitute URLs is fixed in fb4bf72.
>
> The more general problem remains though: for all the other options, like
> max-build-jobs, timeout, etc., the client settings take precedence over
> the daemon settings because the ‘set-build-options’ RPC doesn’t provide
> a way to say “use default value.”

Fixed in commit deac976d3d26c7b85b9c90efb424b0aa94f1027c (at last!) by
moving max-build-jobs, build-cores, and max-silent-time to the optional
key/value option list at the end of ‘set-build-options’.

Ludo’.