From: Gabriel Wicki <gabriel@erlikon.ch>
To: 74980@debbugs.gnu.org
Subject: bug#74980: Home container do not instantiate ~/.guix-profile
Date: Thu, 19 Dec 2024 22:12:44 +0100 [thread overview]
Message-ID: <87zfkrz8ab.fsf@erlikon.ch> (raw)
Hi there!
Invoking a home container does not create ~/.guix-profile (which in my case
is symlinked to ~/.guix-home/profile). This leads to a problem when
testing my Emacs configuration, since I there add
~/.guix-profile/share/emacs/site-lisp to its load path.
I guess referring to ~/.guix-profile seems the smart choice, since it
could also work on home environments where I added the necessary
packages "manually" to my user's profile, so I consider only having
~/.guix-home to be somewhat off.
Any ideas on this? Is this intended behaviour? Is my configuration off?
next reply other threads:[~2024-12-19 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 21:12 Gabriel Wicki [this message]
2024-12-19 21:00 ` bug#74980: [PATCH] home: container: Create symlink to .guix-home/profile Gabriel Wicki
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=87zfkrz8ab.fsf@erlikon.ch \
--to=gabriel@erlikon.ch \
--cc=74980@debbugs.gnu.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 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).