all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Rustand <rustand.lars@gmail.com>
To: help-guix@gnu.org
Cc: Richard <richard@freakingpenguin.com>,
	"Kristoffer Ström" <kristoffer@rymdkoloni.se>
Subject: Re: Include home environment in image
Date: Fri, 19 Jan 2024 14:59:35 +0100	[thread overview]
Message-ID: <871qadfm8v.fsf@yoga.mail-host-address-is-not-set> (raw)
In-Reply-To: <877ck5ig8h.fsf@freakingpenguin.com>


Richard <richard@freakingpenguin.com> writes:

> +1 for upstreaming if possible. Being able to associate home
> environments with a system declaration would be very helpful. I remember
> someone asking about guix deploy and home environments, so it seems to
> be a popular feature request.

This reminds me of an idea I've had for some time. It would be nice to
have a separate deploy command to be able to remotely deploy only a home
config. So instead of running `guix deploy system.scm` you could do
`guix deploy-home home.scm`.

> There are edge cases where the two need to be kept in sync. (e.g.
> StumpWM. The package needs to be added at a system level so login
> managers see it, but configuration needs to be in the user's home.
> Upgrade the system package with a new SCBL version without upgrading
> your home and StumpWM will complain about compiled files being for the
> wrong version.)

Nice to see a fellow StumpWM user! I have some questions regarding how
to manage loading of asdf dependencies from a read-only filesystem, but I
might start a new thread for this.


      reply	other threads:[~2024-01-19 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27  8:27 Include home environment in image Lars Rustand
2023-12-31 23:06 ` Kristoffer Ström
2024-01-19 11:31   ` Lars Rustand
2024-01-19 13:51     ` Richard
2024-01-19 13:59       ` Lars Rustand [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=871qadfm8v.fsf@yoga.mail-host-address-is-not-set \
    --to=rustand.lars@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=kristoffer@rymdkoloni.se \
    --cc=richard@freakingpenguin.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.