From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: Christopher Lemmer Webber <cwebber@dustycloud.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 15:33:20 -0400 [thread overview]
Message-ID: <87a7d4bl6n.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <878ssovgw5.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Tue, 23 Jul 2019 12:45:46 -0400")
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Chris,
Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
> Maybe a good idea... let me think. Is there any case where we start
> taking actions *before* we might probe a machine that we can think of?
>
> How would we also probe it? Is there a chance of our probing behaving
> incorrectly? That would also be bad, if so.
None that come to mind right now, and if there are any, I don't think
they would be affected by the probing -- aside from doing work that
would get thrown out when the script errors out.
As for the safety of probing, none of the tests I intend on implementing
are effectful. It would be equivalents for 'check-mapped-devices',
'check-file-system-availability', and 'check-initrd-modules', all of
which do little beyond looking at the devices available on the system,
and now a check that would read '%current-system'.
> Another route is to have the user specify what architecture they think
> the machine has, and instead the probing is a "safety check"?
That'd work too, but I feel it's better to avoid putting an unnecessary
burden on the user.
Regards,
Jakob
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-07-23 19:37 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 [this message]
2019-07-23 21:59 ` Ricardo Wurmus
2019-07-24 0:11 ` Jakob L. Kreuze
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=87a7d4bl6n.fsf@sdf.lonestar.org \
--to=zerodaysfordays@sdf.lonestar.org \
--cc=36738@debbugs.gnu.org \
--cc=cwebber@dustycloud.org \
--cc=iyzsong@member.fsf.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).