unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Joe Hillenbrand <joehillen@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Manage ssh public keys?
Date: Fri, 10 Apr 2015 22:17:30 +0200	[thread overview]
Message-ID: <87zj6fwxet.fsf@gnu.org> (raw)
In-Reply-To: <CANJQ5C6CN-=QNF6rKPX26ZQsw75WkPiEtESo+xLbv9Hnr=oUPw@mail.gmail.com> (Joe Hillenbrand's message of "Fri, 10 Apr 2015 09:47:30 -0700")

Joe Hillenbrand <joehillen@gmail.com> skribis:

> Something to keep in mind is what a user means when they add a "files"
> argument to user-account. I take this to mean "I want the operating
> system configurations to manage this file, not the user", which to me
> means, clobber a file if it is already there and symlink it to
> /gnu/store.

Yes.

> The question then is, what happens when the configuration changes from
> having a "files" argument to not having one. What happens to the
> links?

Good point.  I’d say we just remove the symlinks.

> Also on the topic of a "files" option, what about managing a
> collection of files, like a directory of dotfiles or ~/.emacs? Would
> it be possible to use this option with something like "git-fetch"?

It would be possible yes.  Behind the scenes it would use gexp, so any
object whose type has a “gexp compiler” can be used (this includes
<package>, <origin>, and <local-file>.)

I’ll see what I can do if nobody beats me at it.

Thanks,
Ludo’.

  reply	other threads:[~2015-04-10 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  1:01 Manage ssh public keys? Joe Hillenbrand
2015-04-09 11:51 ` David Thompson
2015-04-09 12:00 ` Ludovic Courtès
2015-04-09 15:34   ` Joe Hillenbrand
2015-04-09 19:29     ` Ludovic Courtès
2015-04-10  9:28       ` 宋文武
2015-04-10 14:21         ` Ludovic Courtès
2015-04-10 14:24           ` David Thompson
2015-04-10 16:47           ` Joe Hillenbrand
2015-04-10 20:17             ` Ludovic Courtès [this message]
2015-04-10 20:45               ` David Thompson
2015-04-11 19:55                 ` Ludovic Courtès

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=87zj6fwxet.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=joehillen@gmail.com \
    /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).