From: Richard Sent <richard@freakingpenguin.com>
To: "Ludovic Courtès" <ludo@gnu.org>
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: Mon, 29 Apr 2024 11:21:44 -0400 [thread overview]
Message-ID: <87il00yz1z.fsf@freakingpenguin.com> (raw)
In-Reply-To: <87le4w1e2l.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 29 Apr 2024 15:41:22 +0200")
Hi Ludo!
Ludovic Courtès <ludo@gnu.org> writes:
> Ludovic Courtès <ludo@gnu.org> skribis:
>
> Silly me: I was using ‘home-service-type’ instead of
> ‘guix-home-service-type’. 🤦
>
> (Interestingly, this has no effect at all, but nothing complained,
> either.)
>
> Works like a charm after switching to ‘guix-home-service-type’! :-)
Thanks for the response! I just started investigating that and was close
to entering the "losing my mind" phase of debugging. Glad to hear it
does in fact work!
>> 2. ‘guix home describe’ isn’t prepared to deal with that: it returns
>> information from the last
>> /var/guix/profiles/per-user/$USER/guix-home-*.
>
> That issue remains, but it’s less of a problem.
There are definitely some potential issues when running certain 'guix
home ...' commands that operate on generations while using
'guix-home-service. The "correct" behavior may not always be obvious
either. For example:
1. 'guix-home-service' reactivates the same home environment every time
the service is launched. If generations are created, how should that be
reflected if the user has a home environment activated by
'guix-home-service' (generation A), runs 'guix home reconfigure'
(generation B), and reboots? Consider it a silent roll back to A? Should
B be marked a garbage collection candidate? Or should generation C be
created?
2. Users may try 'guix home roll-back' or 'switch-generations', thinking
the change is persistent. Should this be transient? Or should the change
be made persistent somehow? (I'm strongly in favor of "transient", but I
figured I'd raise the point.)
I think this approach is best:
1. Create a new home generation when 'guix system reconfigure' and
'guix-home-service' are used.
2. Make 'guix home reconfigure', 'switch-generations', and 'roll-back'
all warn that the changes are temporary.
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.
4. Adjust 'guix home list-generations' and 'describe' to indicate if a
home generation came from a particular system generation.
As for how to accomplish this or how feasible it is? No clue.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
next prev parent reply other threads:[~2024-04-29 15:22 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 [this message]
2024-05-25 13:04 ` 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=87il00yz1z.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=69781@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=ludo@gnu.org \
--cc=paren@disroot.org \
--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.