From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Error messages and progress report
Date: Wed, 12 Dec 2012 00:15:37 +0100 [thread overview]
Message-ID: <87vcc8ch9i.fsf@gnu.org> (raw)
In-Reply-To: <201212111640.43153.andreas@enge.fr> (Andreas Enge's message of "Tue, 11 Dec 2012 16:40:42 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> Am Dienstag, 11. Dezember 2012 schrieb Ludovic Courtès:
>> Anyway, what does work is something like:
>> $ guix-package --profile=$HOME/.guix-profile --install=hello
>
> This worked, but in a rather strange way. .guix-profile did not exist
> yet. It was created as a symbolic link to the new file
> .guix-profile-1-link, itself a symbolic link to
> /nix/store/1n6bpxkjq2w1m8nlyc6c6bpf0y8rspi0-user-environment .
>
> I deleted the redirection and let .guix-profile point to /nix/store/...
> directly. Then adding a second package recreates the previous situation,
> with .guix-profile-1-link pointing to a different user environment
> in /nix/store. And after removing the second package, I get a
> .guix-profile-2-link pointing to the previous user environment in
> /nix/store. Interesting!
This is expected. As with nix-env, there’d normally be a
~/.guix-profile pointing to
/nix/var/nix/profiles/per-user/$USER/profile, which would itself point
to profile-X-link in the same directory (where X is the generation
number.) So what you’re observing is basically this.
> As for the rough edges, installing the hello package twice results in
> an error message, too.
Commit 1c67d63 fixes that.
> Another question: My guix source and compile directory gets populated
> with symbolic links t-profile* to files /nix/store/*user-environment
> that survive even to "make distclean". I suppose I can safely delete them?
> If yes, could they be deleted by "make clean"?
Yes. These were leftovers from tests/guix-package.sh. I think 7a6548c
solves that.
Thanks!
Ludo’.
next prev parent reply other threads:[~2012-12-11 23:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 20:01 Error messages and progress report Andreas Enge
2012-12-09 20:50 ` Ludovic Courtès
2012-12-10 9:19 ` Andreas Enge
2012-12-10 13:26 ` Ludovic Courtès
2012-12-10 18:17 ` Andreas Enge
2012-12-10 21:29 ` Ludovic Courtès
2012-12-10 22:12 ` Andreas Enge
2012-12-10 22:59 ` Ludovic Courtès
2012-12-10 23:22 ` Andreas Enge
2012-12-11 12:22 ` Andreas Enge
2012-12-11 13:20 ` Nikita Karetnikov
2012-12-11 14:37 ` Ludovic Courtès
2012-12-11 15:40 ` Andreas Enge
2012-12-11 21:15 ` Andreas Enge
2012-12-11 23:16 ` Ludovic Courtès
2012-12-12 8:55 ` Andreas Enge
2012-12-13 19:17 ` Andreas Enge
2012-12-11 23:15 ` Ludovic Courtès [this message]
2012-12-12 8:48 ` Andreas Enge
2012-12-12 13:14 ` Ludovic Courtès
2013-01-06 17:49 ` Ludovic Courtès
2013-01-10 9:56 ` Andreas Enge
2013-01-10 10:45 ` Andreas Enge
2013-01-10 21:14 ` Ludovic Courtès
2013-01-11 13:49 ` Andreas Enge
2013-01-11 14:58 ` Ludovic Courtès
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=87vcc8ch9i.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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).