unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 71802@debbugs.gnu.org, andrew@trop.in
Subject: [bug#71802] [PATCH 0/1] Avoid guix home reconfiguration when nothing is to be done.
Date: Fri, 28 Jun 2024 21:08:20 -0400	[thread overview]
Message-ID: <87bk3kv9mj.fsf@freakingpenguin.com> (raw)
In-Reply-To: <20240627150643.30981-1-ngraves@ngraves.fr> (Nicolas Graves's message of "Thu, 27 Jun 2024 17:00:40 +0200")

Hi Nicolas,

> While experimenting with profile reconfigurations almost a year ago, a
> thing that happened a lot was that I reconfigured a lot while often I
> didn't need to. In the event a guix system / guix home wrapper comes
> to life (I've experimented for that in RDE), such a reflex to avoid
> switching to new profiles that already are existing profiles is
> welcome IMO.
>
> This is not a definitive proposal but rather an illustration of an
> approach which could be implemented at other places too to avoid some
> unecessary calculations / reconfigurations.

I can't figure out exactly how this patch could apply, but I can see it
or something similar being useful when using guix-home-service. If we
can make oneshot service attempt to register a new generation on every
invocation /and/ use a patch like to avoid redundant generations, it may
solve many of the issues raised in [1].

[1]: https://issues.guix.gnu.org/69781#5

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.




      parent reply	other threads:[~2024-06-29  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 15:00 [bug#71802] [PATCH 0/1] Avoid guix home reconfiguration when nothing is to be done Nicolas Graves via Guix-patches via
2024-06-27 15:36 ` [bug#71802] [PATCH] guix: home: Avoid " Nicolas Graves via Guix-patches via
2024-06-29  1:08 ` Richard Sent [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87bk3kv9mj.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=71802@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=ngraves@ngraves.fr \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).