From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: drashne@protonmail.com, 28749@debbugs.gnu.org
Subject: bug#28749: guix build --subsitute-urls does not override guix-daemon run with --no-subsitutes
Date: Fri, 13 Oct 2017 17:54:30 -0400 [thread overview]
Message-ID: <20171013215430.GA1951@jasmine.lan> (raw)
In-Reply-To: <87tvz3f8sp.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Fri, Oct 13, 2017 at 09:59:18AM -0400, Maxim Cournoyer wrote:
> Although, I would argue that the current behavior is
> non-intuitive. While true that the manual skim about how one can achieve
> this, the reference to "The Store" is not helpful; it doesn't even
> mention the "set-build-options" procedure. Also, leaving the command
> line to plug directly into Guix's API from Guile is inconvenient at best.
>
> It seems to me that the current behavior of other options that affect
> the guix-daemon operation are that user options override the
> corresponding guix-daemon defaults; maybe that's what lead me and others
> to think that --substitute-urls should attempt to do what the user
> desires?
Yeah, maybe it should be changed to be consistent with the behavior of
the other options.
> Otherwise, we could at least give advice on the output of a Guix command
> when the user passed --substitute-urls when the guix-daemon substitutes
> were disabled to make this clear(er).
Agreed, we should at least do that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-13 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 17:13 bug#28749: guix build --subsitute-urls does not override guix-daemon run with --no-subsitutes Drashne
2017-10-09 19:20 ` Leo Famulari
2017-10-13 13:59 ` Maxim Cournoyer
2017-10-13 21:54 ` Leo Famulari [this message]
2017-10-14 13:23 ` Ricardo Wurmus
2017-10-14 16:41 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171013215430.GA1951@jasmine.lan \
--to=leo@famulari.name \
--cc=28749@debbugs.gnu.org \
--cc=drashne@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.