From: Zacchaeus Scheffer <zaccysc@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 53886@debbugs.gnu.org
Subject: bug#53886: guix home not respecting guix pull -C
Date: Wed, 9 Feb 2022 13:17:23 -0500 [thread overview]
Message-ID: <CAJejy7m=P-Rct80e9OySGK74tq7s=s1b64+n7Nk4Ec_XrZqGiA@mail.gmail.com> (raw)
In-Reply-To: <87wni4mmmf.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
>
> I believe that's the main misunderstanding here, `guix home` acts like
> `guix system`: it creates home generations, inside which there is a
> profile. That profile is _not_ ~/.guix-profile, but rather
> ~/.guix-home/profile. They are disjoint and not operated on by the same
> commands, guix home will not touch ~/.guix-profile. If you configure
> your shell environment variables with guix home alone, I believe only
> the the guix home profile is available by default.
>
I think I tracked down the problem. In my home-zsh-service, I added the
contents of my previous .zprofile to to my new .zprofile, including "source
/etc/profile", so my .zprofile (with autogenerated lines) looked like:
source /etc/profile
source ~/.profile
source /etc/profile
Basically, /etc/profile stripped from my PATH the ~/.guix-home/profile
which was added by ~/.profile
I think this solves the original problem, but I don't like that
~/.guix-profile/ AND ~/.guix-home/profile are added to your path by
default. I admit this is probably a "sane default" for most users, but I
care a lot about reproducibility. Though I think there should be a better
solution, for now I am going to have guix home run "guix package -m" with
an empty manifest on reconfigure.
Thanks all for your help,
Zacchaeus
[-- Attachment #2: Type: text/html, Size: 1657 bytes --]
prev parent reply other threads:[~2022-02-09 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 23:57 bug#53886: guix home not respecting guix pull -C Zacchaeus Scheffer
2022-02-09 1:06 ` Leo Famulari
2022-02-09 6:40 ` Zacchaeus Scheffer
2022-02-09 9:10 ` Josselin Poiret via Bug reports for GNU Guix
2022-02-09 18:17 ` Zacchaeus Scheffer [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='CAJejy7m=P-Rct80e9OySGK74tq7s=s1b64+n7Nk4Ec_XrZqGiA@mail.gmail.com' \
--to=zaccysc@gmail.com \
--cc=53886@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
/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).