all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>
Cc: 69781@debbugs.gnu.org, paren@disroot.org,
	Tanguy Le Carrour <tanguy@bioneland.org>,
	rustand.lars@gmail.com, Andrew Tropin <andrew@trop.in>
Subject: [bug#69781] [PATCH v2] services: Add the Guix Home Service
Date: Sat, 25 May 2024 15:04:26 +0200	[thread overview]
Message-ID: <87v83211r9.fsf@gnu.org> (raw)
In-Reply-To: <87il00yz1z.fsf@freakingpenguin.com> (Richard Sent's message of "Mon, 29 Apr 2024 11:21:44 -0400")

Hi!

Richard Sent <richard@freakingpenguin.com> skribis:

> I think this approach is best:
>
> 1. Create a new home generation when 'guix system reconfigure' and
> 'guix-home-service' are used.

Yes.  That would placate ‘guix home describe’.

> 2. Make 'guix home reconfigure', 'switch-generations', and 'roll-back'
> all warn that the changes are temporary.

How could they know, though?

> 3. Disable 'guix home delete-generations' on any system-created home
> generations. System-created home generations are deleted when the
> corresponding system generation is deleted.

Same question here.

In short: adding an activation snippet that creates a new Home
generation should be an improvement.

Thanks!

Ludo’.




      reply	other threads:[~2024-05-25 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 18:41 [bug#69781] [PATCH] services: Add the Guix Home Service Richard Sent
2024-03-21 18:36 ` [bug#69781] [PATCH v2] " Richard Sent
2024-04-17 10:18   ` bug#69781: " Ludovic Courtès
2024-04-29 10:14   ` [bug#69781] " Ludovic Courtès
2024-04-29 13:41     ` Ludovic Courtès
2024-04-29 15:21       ` Richard Sent
2024-05-25 13:04         ` Ludovic Courtès [this message]

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=87v83211r9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=69781@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=paren@disroot.org \
    --cc=richard@freakingpenguin.com \
    --cc=rustand.lars@gmail.com \
    --cc=tanguy@bioneland.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 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.