GNU bug report logs - #36738
[PATCH] guix deploy: Support '--no-grafts' and '--system'

Previous Next

Full log

Message #23 received at 36738 <at> debbugs.gnu.org (full text, mbox):

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: Christopher Lemmer Webber <cwebber <at> dustycloud.org>
Cc: 36738 <at> debbugs.gnu.org, 宋文武 <iyzsong <at> member.fsf.org>,
 "Thompson, David" <dthompson2 <at> worcester.edu>,
 Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: [bug#36738] [PATCH] guix deploy: Support '--no-grafts' and
 '--system'
Date: Tue, 23 Jul 2019 15:33:20 -0400

[Message part 1 (text/plain, inline)]

Hi Chris,

Christopher Lemmer Webber <cwebber <at> 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

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.