From: Ryan Prior <ryanprior@hey.com>
To: Andrew Tropin <andrew@trop.in>, Joshua Branson <jbranso@dismail.de>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>
Subject: Re: guix home
Date: Mon, 15 Mar 2021 02:15:28 +0000 [thread overview]
Message-ID: <c2f94d4a0e5ffece62045a5b47434a6de525e937@hey.com> (raw)
In-Reply-To: <87pn01agb4.fsf@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On March 14, 2021, Joshua Branson <jbranso@dismail.de> wrote:
> Andrew Tropin <andrew@trop.in> writes:
>
> > There is an implementation of `guix home` subcommand, which behaves
> > similar to `guix system`
Thanks for sharing this Andrew, it looks awesome & I'm going to give it
a try!
What do you think about changing the command? It manages user files,
user services, user environment variables, the lifecycle of user
sessions. So we could have "guix system" for system-level things, and
"guix user" for user-level things. Similarly, many of the services you
describe sound to me like they would be easier to understand what they
do with names like "user-service," "user-environment-vars," etc.
I feel Guix needs something like this upstream. Whether this is the
right implementation or not I'm not qualified to judge, but I'll read
the source code and see what I can learn or contribute!
Ryan
[-- Attachment #2: Type: text/html, Size: 3416 bytes --]
next prev parent reply other threads:[~2021-03-15 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 6:09 guix home Andrew Tropin
2021-03-14 15:46 ` Joshua Branson
2021-03-15 2:15 ` Ryan Prior [this message]
2021-03-16 8:23 ` Andrew Tropin
2021-03-15 16:51 ` Ludovic Courtès
2021-03-15 20:16 ` Julien Lepiller
2021-03-19 8:18 ` Andrew Tropin
2021-03-16 9:09 ` 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=c2f94d4a0e5ffece62045a5b47434a6de525e937@hey.com \
--to=ryanprior@hey.com \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
/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).