From: Andrew Tropin <andrew@trop.in>
To: Raghav Gururajan <rg@raghavgururajan.name>, 56610@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#56610: Guix Home placing dotfiles in wrong directory.
Date: Mon, 18 Jul 2022 09:31:19 +0300 [thread overview]
Message-ID: <87v8rv53uw.fsf@trop.in> (raw)
In-Reply-To: <4f8337c4-4623-7c0f-5c48-8d1f14c08567@raghavgururajan.name>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On 2022-07-17 03:07, Raghav Gururajan via Bug reports for wrote:
> Hello Guix,
>
> home-files-service-type is placing configuration files in `~/config/foo`
> instead of `~/.config/foo`.
>
> For example, the following guix-home service should place the git
> configuration in ~/.config/git`. But it creates a new directory
> `~/config/git` and places the file there.
It's intended https://yhetil.org/guix-devel/87v8w2se04.fsf@trop.in/
Updates to the documentation is on the way:
https://yhetil.org/guix-patches/87h74abbn6.fsf@trop.in/
>
> (simple-service 'git-config
> home-files-service-type
In this case, it's better to use home-xdg-configuration-files instead of
home-files.
> (list
> `("config/git/config"
> ,(local-file
> (string-append (getenv "HOME")
Just a tip for finer reproducibility of the configuration: it's better
to avoid using environment variables, files outside of the project
directory and other thing, which make code impure/dependening on global
state.
> "/dotfiles/git/config")))))
>
> It started happening recently, so will try to bisect.
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-07-18 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 7:07 bug#56610: Guix Home placing dotfiles in wrong directory Raghav Gururajan via Bug reports for GNU Guix
2022-07-17 8:34 ` Oleg Pykhalov
2022-07-18 6:31 ` Andrew Tropin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8rv53uw.fsf@trop.in \
--to=andrew@trop.in \
--cc=56610@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rg@raghavgururajan.name \
/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.