unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Giacomo Leidi <goodoldpaul@autistici.org>
Cc: paren@disroot.org, 68848-done@debbugs.gnu.org,
	Andrew Tropin <andrew@trop.in>,
	68857-done@debbugs.gnu.org
Subject: bug#68848: bug#68857: gnu: home: dotfiles: Avoid creating extra directory in $HOME.
Date: Wed, 06 Mar 2024 23:15:03 +0100	[thread overview]
Message-ID: <87v85z6m8o.fsf_-_@gnu.org> (raw)
In-Reply-To: <a1ad5e20a171804eea603bc33cde2e0f4a86b113.1709758362.git.goodoldpaul@autistici.org> (Giacomo Leidi's message of "Wed, 6 Mar 2024 21:52:42 +0100")

Hi,

Giacomo Leidi <goodoldpaul@autistici.org> skribis:

> The current implementation of the home-dotfiles-service-type contradicts
> the Guix manual (see https://issues.guix.gnu.org/68848 ). This patch
> properly implements both the plain and Stow dotfiles directory layouts.
>
> It does so by refactoring home-dotfiles-configuration adding a new
> packages field to support GNU Stow's users workflow and introducing
> a new layout field to switch between the two directory layouts.
>
> * gnu/home/services/dotfiles (home-dotfiles-configuration): Migrate to
> (gnu services configuration);
> [packages]: new field;
> [layout]: new field;
> (strip-stow-dotfile): new variable;
> (strip-plain-dotfile): new variable;
> (home-dotfiles-configuration->files): use the new fields;
> [directory-contents]: allow for
> selecting a subset of application dotfile directories;
> * doc/guix.texi: document the new layouts.
>
> Change-Id: I2e96037608353e360828290f055ec5271cfdfd48

Applied, thanks again!

Ludo’.




           reply	other threads:[~2024-03-06 22:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <a1ad5e20a171804eea603bc33cde2e0f4a86b113.1709758362.git.goodoldpaul@autistici.org>]

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=87v85z6m8o.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=68848-done@debbugs.gnu.org \
    --cc=68857-done@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=goodoldpaul@autistici.org \
    --cc=paren@disroot.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).