--- Begin Message ---
Subject: |
Installing, then removing, a package yields a different profile |
Date: |
Mon, 05 Nov 2018 22:25:46 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hi,
I've noticed that if I do the following...
guix package -p .guix-profile -i hello
guix package -p .guix-profile -i coreutils
guix package -p .guix-profile -r coreutils
...I get profile generations like the following:
.guix-profile-1-link -> /gnu/store/mbvwb1pv8ps0l39gil41g4zj3khx3r8p-profile
.guix-profile-2-link -> /gnu/store/m6cwnnxcccnd8bga52jxn74vm67n7ry1-profile
.guix-profile-3-link -> /gnu/store/qfpmx9rz7kxa8w8r2pz4vj8ilbi70dcp-profile
However, the 1st and 3rd generations are practically the same:
--8<---------------cut here---------------start------------->8---
$ diff -r /gnu/store/mbvwb1pv8ps0l39gil41g4zj3khx3r8p-profile
/gnu/store/qfpmx9rz7kxa8w8r2pz4vj8ilbi70dcp-profile
diff -r /gnu/store/mbvwb1pv8ps0l39gil41g4zj3khx3r8p-profile/etc/profile
/gnu/store/qfpmx9rz7kxa8w8r2pz4vj8ilbi70dcp-profile/etc/profile
11c11
< export
PATH="${GUIX_PROFILE:-/gnu/store/mbvwb1pv8ps0l39gil41g4zj3khx3r8p-profile}/bin${PATH:+:}$PATH"
---
> export
> PATH="${GUIX_PROFILE:-/gnu/store/qfpmx9rz7kxa8w8r2pz4vj8ilbi70dcp-profile}/bin${PATH:+:}$PATH"
[1] address@hidden:/tmp/tmp.ZOTdkBr4rD
$
--8<---------------cut here---------------end--------------->8---
Now, this isn't really a problem, since it isn't wasting space, and it
doesn't take long to build. It's more of a curiosity. Why is it that
profile generations 1 and 3 don't both point to the same profile in the
store? Is this expected behavior?
I wasn't sure what would happen when I tried this. I had guessed
(incorrectly) that generation 3 would point to the same profile that had
been built for generation 1, so I was a little surprised by this.
--
Chris
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#33285: Installing, then removing, a package yields a different profile |
Date: |
Tue, 12 Mar 2019 12:58:59 +0100 |
User-agent: |
mu4e 1.0; emacs 26.1 |
Chris Marusich <address@hidden> writes:
> Thinking about it that way, I agree it makes sense as is. I think it's
> valid to say this isn't a bug, then.
Okay, I’m closing this bug.
Thanks for bringing this up!
--
Ricardo
--- End Message ---