GNU bug report logs - #75414
[PATCH 0/2] Add roll-back action to guix deploy

Previous Next

Package: guix-patches;

Reported by: Arun Isaac <arunisaac <at> systemreboot.net>

Date: Tue, 7 Jan 2025 00:19:02 UTC

Severity: normal

Tags: patch

Done: Arun Isaac <arunisaac <at> systemreboot.net>

Bug is archived. No further changes may be made.

Full log


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

From: Evgeny Pisemsky <mail <at> pisemsky.site>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: arunisaac <at> systemreboot.net, 75414 <at> debbugs.gnu.org
Subject: Re: [bug#75414] [PATCH 2/2] deploy: Add roll-back action.
Date: Fri, 31 Jan 2025 22:01:00 +0300
Ludovic Courtès <ludo <at> gnu.org> writes:

>> To me this is more flexible than one command that does everything. I
>> can imagine a situation when I just need to run some command on all
>> machines without reconfiguring them, which is currently impossible.
>
> It’s possible:
>
>   guix deploy machines.scm -x -- herd restart something

This is funny and sad at the same time, because I thought that this
option works like some kind of post-deploy hook, not separate action.

The reasons are how documentation puts it and how those commands look:
the verb "deploy" just make one think it always deploys. Confusing UI.

If my opinion matters, for the current =guix deploy= interface keep
adding actions as options, explicitly stating them as separate actions
in documentation. If/when the decision to introduce =guix machine= UI
will be made, it would be better to implement actual actions there -
like in the transition from =guix environment= to =guix shell=.




This bug report was last modified 145 days ago.

Previous Next


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