all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 53486@debbugs.gnu.org
Subject: [bug#53486] [PATCH] deploy: Add '--execute'.
Date: Mon, 31 Jan 2022 23:44:05 +0100	[thread overview]
Message-ID: <874k5ja5l6.fsf_-_@gnu.org> (raw)
In-Reply-To: <87tudmheby.fsf@gmail.com> (Oleg Pykhalov's message of "Sat, 29 Jan 2022 16:16:33 +0300")

Hi,

Oleg Pykhalov <go.wigust@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
> […]
>
>> Here's a simple but handy option for ‘guix deploy’.
>>
>> One of the primary use cases for me is being able to run ‘herd
>> restart XYZ’ after deployment, but I’m also thinking of adding
>> special support for such things in <machine>:
>
> I think for non ‘guix deploy’ users such functionality should exist,
> too.  Otherwise the users could use ‘guix deploy’ by deploying to
> localhost instead of ‘guix system reconfigure’.  So to avoid this we
> need such things in <operating-system>.

So that ‘guix system reconfigure’ would unconditionally refer the
Shepherd services you specify?

It’s a bit “weird”, because that information has to do with “state
transition” more than about the OS config, but why not.  Actually
‘unattended-service-type’ already has such a list, so it does seem like
the pattern comes up several times.  Hmm!

Ludo’.




  reply	other threads:[~2022-01-31 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 21:21 [bug#53486] [PATCH] deploy: Add '--execute' Ludovic Courtès
2022-01-29 13:16 ` Oleg Pykhalov
2022-01-31 22:44   ` Ludovic Courtès [this message]
2022-01-31 22:48 ` Ricardo Wurmus
2022-02-01 19:32   ` Ludovic Courtès
2022-02-01 20:08     ` Ricardo Wurmus
2022-02-02 17:44       ` bug#53486: " Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=874k5ja5l6.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53486@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.