From: "Ludovic Courtès" <ludo@gnu.org>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: help-guix@gnu.org
Subject: Re: Modify Channels for all users
Date: Sat, 01 Jun 2019 16:04:49 +0200 [thread overview]
Message-ID: <87pnnxe70e.fsf@gnu.org> (raw)
In-Reply-To: <e8fdcd04-4462-457a-b4af-5b3536d0125a@www.fastmail.com> (Reza Alizadeh Majd's message of "Mon, 27 May 2019 09:58:29 +0430")
Hi,
"Reza Alizadeh Majd" <r.majd@pantherx.org> skribis:
> I just aware about that copying the skeleton files is a one time operation, we can't modify
> skeleton files later with a new system configuration file for existing users. do we have any
> solution to copy skeleton files to existing users home directories on each execution of
> guix system reconfigure ?
If you modify these files at each reconfigure, they’re no longer
skeletons. :-) I would advise against it.
Now, you could very much add an “activation snippet” that forcefully
copies files to the user home directories at each boot.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-06-01 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 8:55 Modify Channels for all users Reza Alizadeh Majd
2019-05-24 20:26 ` Oleg Pykhalov
2019-05-25 11:02 ` Reza Alizadeh Majd
2019-05-26 19:36 ` Ludovic Courtès
2019-05-27 5:28 ` Reza Alizadeh Majd
2019-06-01 14:04 ` Ludovic Courtès [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=87pnnxe70e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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.
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).