From: Andrew Tropin <andrew@trop.in>
To: Ryan Prior <ryanprior@hey.com>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>
Subject: Re: guix home
Date: Tue, 16 Mar 2021 11:23:04 +0300 [thread overview]
Message-ID: <CABrWRW3fGiAD0KEP9xcN-CnjCqmzxooVQExx8-KO5OwMQAsNNw@mail.gmail.com> (raw)
In-Reply-To: <c2f94d4a0e5ffece62045a5b47434a6de525e937@hey.com>
Joshua Branson <jbranso@dismail.de> writes:
> I'll have to give your guix home command a try! It sounds easy!
One of the goals is to make it effortless to use) For now we still
implement services for basic software and some fundamental features, but
in a couple of weeks plan to invite few more people to actively use
`guix home`. Follow the news on rde-announces mailing list [fn:1].
Thank you for kind supportive words!
Ryan Prior <ryanprior@hey.com> writes:
> Thanks for sharing this Andrew, it looks awesome & I'm going to give it
> a try!
You are very welcome!)
> 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.
I don't have very strong preference here and open for discussion, but
will provide my rationale for original naming:
- `guix system` manages operating systems and its generations and stuff.
- `guix package` installs, removes, upgrades packages.
Following this convention `guix user` would have to manage users, while
`guix home` manages user's home folders and related stuff. I find home
subcommand more suitable here, however other internal naming may be
temporary and is a subject to change if better options are found.
> 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.
It's maybe true, however, the other benefit of home- naming is it makes
all the related concepts distinct. It will be harder to confuse
home-services with systemd user service for example. Still have to work
on a better naming in some places.
> 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!
All the contributions from discussions to patches are welcome!)
* Footnotes
[fn:1] https://lists.sr.ht/~abcdw/rde-announce
--
Best regards,
Andrew Tropin
next prev parent reply other threads:[~2021-03-16 8:23 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
2021-03-16 8:23 ` Andrew Tropin [this message]
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=CABrWRW3fGiAD0KEP9xcN-CnjCqmzxooVQExx8-KO5OwMQAsNNw@mail.gmail.com \
--to=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=ryanprior@hey.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).