unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Daniel Meißner" <daniel.meissner-i4k@rub.de>
To: Holger Peters <holger.peters@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: How is .guix-home created?
Date: Sat, 16 Oct 2021 15:09:34 +0200	[thread overview]
Message-ID: <4E865124-8E39-4A99-82D0-5D212E8A7E17@rub.de> (raw)
In-Reply-To: <678EF792-182B-41EC-A32E-7C65E82BDB9D@posteo.de>

Hi Holger,

Holger Peters schreibt:
>So, I am running guix on top of a Debian testing, just to provide the
>context that I am operating in. I found
>https://guix.gnu.org/manual/devel/en/html_node/Home-Configuration.html
>and what is missing is how the ~/.guix-home directory is created (I
>assume it is created by .guix-home). Or, to phrase it from another angle,
>how do I connect the home-configuration as in
>https://guix.gnu.org/manual/devel/en/html_node/Declaring-the-Home-Environment.html
>with guix-home.

The ~/.guix-home directory is created by the `guix home' command automatically. The manual says:

> The home environment is configured by providing a home-environment declaration in a file that can be passed to the guix home command (see Invoking guix home).

So, after you wrote your home-enviroment declaration, say in the file myhome.scm, you'd invoke

$ guix home reconfigure myhome.scm

which will create the ~/.guix-home directory as well as the appropiate ~/.bash_profile file if your home-environment also contains a shell configuration (this is recommended). No worries about existing config files, guix home will back them up for you.

Best
Daniel


      parent reply	other threads:[~2021-10-16 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16  5:54 How is .guix-home created? Holger Peters
2021-10-16 12:35 ` Oleg Pykhalov
2021-10-19 20:03   ` Holger Peters
2021-10-16 13:09 ` Daniel Meißner [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=4E865124-8E39-4A99-82D0-5D212E8A7E17@rub.de \
    --to=daniel.meissner-i4k@rub.de \
    --cc=help-guix@gnu.org \
    --cc=holger.peters@posteo.de \
    /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.
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).