all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: 宋文武 <iyzsong@gmail.com>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: (Not GuixSD) Purpose of ~/.config/guix/ & config. files
Date: Mon, 21 Sep 2015 09:02:54 +0800	[thread overview]
Message-ID: <CAHZE2pfPOidWvmDJdcpkz8r3YmrZzAmphJehK+DdyCm3SBEkYA@mail.gmail.com> (raw)
In-Reply-To: <CAMfbzvBE5vyph7k3vXfCFNQy4p-pu1jZA38E2MppjzGvuXdPmw@mail.gmail.com>

2015-09-21 2:45 GMT+08:00 Vicente Vera <vicentemvp@gmail.com>:
> Hello.
>
> After running 'guix pull' (as root) with a fresh binary installation
> directory ~root/.config/guix/ was created, which contains a "latest"
> symlink pointing to /gnu/store/...-guix-latest/.
>
> Since I work as a regular user, I noticed that Guix wasn't picking up
> changes from the updated distribution. Creating a ~luser/.config/guix/
> directory with the same "latest" symlink solved the problem. Now after
> every 'guix pull' I have to manually update the symlink.
Yes, by this way, every user can manage his own guix packages distro.
And I have symlink both to a git checkout of guix.
>
> I was wondering if the ~/.config/guix/ directory is used for something
> else apart from the case described above.
I can't find other thing, but only `latest'.
>
> On another note, what's the appropiate, Guix-y way of storing
> configuration files such as dotfiles, etc. (to be read by Guix
> installed programs) when using Guix atop another GNU/Linux distro?
Guix doesn't have any tricks for those files now.

  reply	other threads:[~2015-09-21  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 18:45 (Not GuixSD) Purpose of ~/.config/guix/ & config. files Vicente Vera
2015-09-21  1:02 ` 宋文武 [this message]
2015-09-23 14:31   ` Vicente Vera

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHZE2pfPOidWvmDJdcpkz8r3YmrZzAmphJehK+DdyCm3SBEkYA@mail.gmail.com \
    --to=iyzsong@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=vicentemvp@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.