Simon Tournier wrote 1 years ago
(address . bug-guix@gnu.org)
87ttqnni9r.fsf@gmail.com
Hi,
Using Guix 6113e05, I notice a behaviour that I do not expect.
Toggle snippet (21 lines)
$ guix shell xterm --dry-run
The following derivation would be built:
/gnu/store/x26rsb69l3jjxczx2ap0i3app6q8prwl-profile.drv
$ which xterm
/usr/bin/xterm
$ guix shell xterm
The following derivation will be built:
/gnu/store/x26rsb69l3jjxczx2ap0i3app6q8prwl-profile.drv
building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building profile with 1 package...
$ which xterm
/gnu/store/9phsgk6m6h7gy09698m5a0s42aqi9yid-profile/bin/xterm
So far, so good.
Now, even if --dry-run is provided, it enters the profile.
Toggle snippet (9 lines)
$ which xterm
/usr/bin/xterm
$ guix shell xterm --dry-run
$ which xterm
/gnu/store/9phsgk6m6h7gy09698m5a0s42aqi9yid-profile/bin/xterm
Well, I thought maybe that’s because --rebuild-cache, but no:
Toggle snippet (9 lines)
$ which xterm
/usr/bin/xterm
$ guix shell xterm --dry-run --rebuild-cache
$ which xterm
/gnu/store/9phsgk6m6h7gy09698m5a0s42aqi9yid-profile/bin/xterm
Well, and I thought that --rebuild-cache redoes the dance:
Toggle snippet (7 lines)
building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building profile with 1 package...
and not, if I do not miss something.
Cheers,
simon