unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
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 13:05:01 -0400	[thread overview]
Message-ID: <CAJ=Rwfb=i0NRqrtxK-RysWy-M902WfPbYupXF3N2iy1VRJYT0g@mail.gmail.com> (raw)
In-Reply-To: <87sgqx8z81.fsf@sdf.lonestar.org>

On Mon, Jul 22, 2019 at 6:48 PM Jakob L. Kreuze
<zerodaysfordays@sdf.lonestar.org> wrote:
>
> zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
> > Great idea. I think that continuing to call the machine's
> > <operating-system> 'system' would be confusing if we introduced the
> > notion of a target architecture, because we use "system" to refer to
> > the target architecture in the rest of Guix's command-line tools.
> > Maybe it would make sense to rename the <operating-system> field to
> > 'os' or something similar, and use the 'system' field to specify the
> > target architecture instead? Any thoughs?
>
> Actually, I had a thought. Why should we make this explicit, when we
> could take an implicit approach and identify the target's architecture
> with 'remote-eval'? Ideally, we'll be probing the machines anyway to
> implement safety checks on the <operating-system> declaration, so why
> not just add this to our list of pre-deployment tests?

I don't see a compelling reason for the architecture to be a part of
the machine data type at this time.  I'd like to avoid such low-level
details if possible because I don't think they will translate well to
more complex methods of deployment.

- Dave

  parent reply	other threads:[~2019-07-23 17:06 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
2019-07-23 17:05     ` Thompson, David [this message]
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='CAJ=Rwfb=i0NRqrtxK-RysWy-M902WfPbYupXF3N2iy1VRJYT0g@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=36738@debbugs.gnu.org \
    --cc=iyzsong@member.fsf.org \
    --cc=zerodaysfordays@sdf.lonestar.org \
    /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).