unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36738@debbugs.gnu.org, 宋文武 <iyzsong@member.fsf.org>
Subject: [bug#36738] [PATCH] guix deploy: Support '--no-grafts' and '--system'
Date: Tue, 23 Jul 2019 20:11:59 -0400	[thread overview]
Message-ID: <8736iw9tps.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <87o91kbefk.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 23 Jul 2019 23:59:11 +0200")

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> I don’t know if this qualifies, but if “guix deploy” were to *create*
> a machine (e.g. on EC2 via the Guile AWS library) it wouldn’t be able
> to probe it first. But in that case we would have full control over
> what the target would be, so no probing would be required.

Ah, good point. I suppose didn't think about this all the way through in
my response -- we wouldn't be able to probe an unprovisioned machine.
But your point gives me even more confidence in the decision to deduce
target architecture at runtime and have that as an environment-specific
check.

Thanks for chiming in!

Regards,
Jakob

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-07-24  0:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20  5:05 [bug#36738] [PATCH] guix deploy: Support '--no-grafts' and '--system' 宋文武
2019-07-22 16:48 ` Jakob L. Kreuze
2019-07-22 22:46   ` Jakob L. Kreuze
2019-07-23 16:45     ` Christopher Lemmer Webber
2019-07-23 19:33       ` Jakob L. Kreuze
2019-07-23 21:59       ` Ricardo Wurmus
2019-07-24  0:11         ` Jakob L. Kreuze [this message]
2019-07-23 17:05     ` Thompson, David
2019-07-23 19:35       ` Jakob L. Kreuze
2019-07-23 16:44   ` Christopher Lemmer Webber
2019-07-23 21:29   ` Ludovic Courtès
2019-07-24 12:36     ` bug#36738: " 宋文武

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736iw9tps.fsf@sdf.lonestar.org \
    --to=zerodaysfordays@sdf.lonestar.org \
    --cc=36738@debbugs.gnu.org \
    --cc=iyzsong@member.fsf.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).