unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 52808@debbugs.gnu.org, Nick Zalutskiy <nick@const.fun>
Subject: bug#52808: Guix home should not assume that all targets are dot files
Date: Sun, 30 Jan 2022 18:13:31 +0100	[thread overview]
Message-ID: <87o83t9mf8.fsf@gnu.org> (raw)
In-Reply-To: <87bkzw2kvm.fsf@trop.in> (Andrew Tropin's message of "Fri, 28 Jan 2022 13:51:57 +0300")

Hi Andrew,

Andrew Tropin <andrew@trop.in> skribis:

> On 2021-12-26 12:17, Nick Zalutskiy wrote:
>
>> The following configuration results in a `~/.run` symlink being
>> created. My expectation is that a `~/run` symlink is created
>> instead. (ie. not a dotfile)
>
> Some how I missed it and not documented home-files-service-type in the
> manual, I'll add it soon.  Thank you for mentioning it.  It should break
> this expectation :)
>
>>> (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:

I share Nick’s surprise.  :-)

[...]

> It's intentional and is a part of a design decision:
>
> For example for ("config/guix/channels.scm" ,(local-file "./chans.scm"))
> chans.scm goes not to ~/.config/guix/channels.scm, but to
> $XDG_CONFIG_DIR/guix/channels.scm, which can be a different location
> from ~/.config, absent dot should partially break this expectation.
>
> It's a bad practice to use something without "config/..."  prefix and
> generally it should be avoided, it still possible to use something
> different in rare use-cases, for example for zsh: ("zshenv"
> ,zshenv-file-like-here), because it's hard to implement the lookup for
> initial configuration file other way for shells.

Oh, I see.

> You can elaborate more on what you try to achieve and I can try to give
> you a recommendation how to implement it.

I’d expect ‘home-files-service-type’ to do just that: add files to the
home directory, without trying to be smart.

Would it make sense to distinguish between ‘home-files’ and (say)
‘home-xdg-configuration-files’?

The latter would copy files to $XDG_CONFIG_DIR at activation time,
whereas the former would just copy them to $HOME.


I’d also suggest removing special handling of HOME/files in
symlink-manager.scm.  Relations between the various components of Guix
Home should preferably be made explicit via service extensions, and not
implicit through conventions like this ‘files’ sub-directory.

Thoughts?

Ludo’.




  parent reply	other threads:[~2022-01-30 17:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 17:17 bug#52808: Guix home should not assume that all targets are dot files Nick Zalutskiy
2022-01-28 10:51 ` Andrew Tropin
2022-01-28 13:33   ` Nick Zalutskiy
2022-01-28 15:22     ` Andrew Tropin
2022-01-30 17:13   ` Ludovic Courtès [this message]
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=87o83t9mf8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=52808@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=nick@const.fun \
    /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).