unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nick Zalutskiy" <nick@const.fun>
To: 52808@debbugs.gnu.org
Subject: bug#52808: Guix home should not assume that all targets are dot files
Date: Sun, 26 Dec 2021 12:17:27 -0500	[thread overview]
Message-ID: <6050c325-9ae9-406a-97fe-91bdf9bcd12a@www.fastmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

The following configuration results in a `~/.run` symlink being created. My expectation is that a `~/run` symlink is created instead. (ie. not a dotfile)

> (home-environment
>   (services
>     (list (service
>             home-bash-service-type
>             (home-bash-configuration
>           (guix-defaults? #t)))
>       (simple-service 'my-files
>               home-files-service-type
>               `(("run" ,(local-file "run")))))))

This applies to all other targets. My expectation is that the configuration should expect the exact target and not make an assumption that all targets are hidden files, since that allows for more utility: 

> (home-environment
>   (services
>     (list (service
>             home-bash-service-type
>             (home-bash-configuration
>               (guix-defaults? #t)))
>           (simple-service 'config-files
>               home-files-service-type
>               `(("run" ,(local-file "run"))
>                 ("README.txt" ,(local-file "README.txt"))
>                 (".config/guix/channels.scm" ,(local-file "config/guix
>                 (".emacs.d/init.el" ,(local-file "emacs.d/init.el"))
>                 (".vimrc" ,(local-file "vimrc"))
>                 (".gitconfig" ,(local-file "gitconfig")))))))

Thank you,

-Nick

[-- Attachment #2: Type: text/html, Size: 3075 bytes --]

             reply	other threads:[~2021-12-26 17:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 17:17 Nick Zalutskiy [this message]
2022-01-28 10:51 ` bug#52808: Guix home should not assume that all targets are dot files Andrew Tropin
2022-01-28 13:33   ` Nick Zalutskiy
2022-01-28 15:22     ` Andrew Tropin
2022-01-30 17:13   ` Ludovic Courtès
2022-02-02  8:10     ` Andrew Tropin
2022-02-08  9:46       ` Ludovic Courtès
2022-02-11 15:52         ` Andrew Tropin
2022-02-26  7:13           ` Andrew Tropin
2022-03-05 22:44           ` Ludovic Courtès
2022-03-09  4:26             ` Andrew Tropin
2022-03-10 10:56               ` Ludovic Courtès
2022-03-11  7:41             ` Andrew Tropin
2022-03-20 18:07               ` Ludovic Courtès
2022-02-08 12:58     ` Xinglu Chen
2022-02-10 20:32       ` Ludovic Courtès
     [not found] ` <handler.52808.D52808.16477996643062.notifdone@debbugs.gnu.org>
2022-03-20 21:00   ` Ludovic Courtès
2022-03-28  9:17     ` Andrew Tropin
2022-03-29  9:51     ` Andrew Tropin
2022-04-10 20:52       ` Ludovic Courtès
2022-03-29 10:24     ` Andrew Tropin
2022-03-30 19:51       ` Ludovic Courtès
2022-04-08 18:18       ` Ludovic Courtès
2022-04-09 14:28         ` Andrew Tropin

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=6050c325-9ae9-406a-97fe-91bdf9bcd12a@www.fastmail.com \
    --to=nick@const.fun \
    --cc=52808@debbugs.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).