From: Andrew Tropin <andrew@trop.in>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: ~abcdw/rde-devel@lists.sr.ht, guix-devel@gnu.org
Subject: Re: Guix Home upstreaming plan
Date: Mon, 03 May 2021 11:13:09 +0300 [thread overview]
Message-ID: <87bl9snskq.fsf@trop.in> (raw)
In-Reply-To: <87o8dwdkc0.fsf@gnu.org>
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> wrote:
> So, I have yet to go ahead and use it for myself to get a better feel.
> In the meantime, I looked at
> <https://guix-home.trop.in/Home-Configuration.html>, and I like what I
> see! It’s great that you already have clear documentation and that
> everything looks consistent with the rest of Guix.
> Since this kind of tool is rather unusual (there’s no real equivalent
> I’m aware of in other distros), I think the manual will have to
> carefully explain what problems this solves and explain why someone
> would want to use it. For example, I think the term “home environment”
> should be defined upfront (I’d summarize it as user configuration files
> + user services, from my reading.)
Sounds reasonable, added a TODO note for that.
> I’m all for it. We’ll have to discuss it together, in particular among
> maintainers, but an option would be to give you commit access for the
> purposes of developing this branch.
Sound good to me. We still have some work to be finished before
upstreaming, but hope we will be good to go by the time other
maintainers will reply.
> I would also like to know what Julien thinks; I think it’s in our
> interest to see cooperation and not competition between the two
> approaches you developed. Julien, WDYT of the plan? More specifically,
> is there anything about the design that you’d like to discuss before we
> go further? Are there guix-home-manager features that could eventually
> make it in Guix Home?
BTW, from time to time people ask about read-only home feature) I reply
that it is theoretically possible, but probably won't be implemented
anytime soon.
> I find the steady progress on Guix Home and the level of polish already
> achieved pretty exciting. If people agree, I think we could aim for
> merging it in the next Guix release, which would leave us a few months.
Thank you for kind words!) A few months should be enough. Looking
forward to see other maintainers thoughts.
> Thank you!
Sure!
next prev parent reply other threads:[~2021-05-03 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 9:09 Guix Home upstreaming plan Andrew Tropin
2021-04-30 12:32 ` Ludovic Courtès
2021-05-01 19:28 ` Xinglu Chen
2021-05-02 21:02 ` Ludovic Courtès
2021-05-03 8:13 ` Andrew Tropin [this message]
2021-05-03 8:14 ` 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=87bl9snskq.fsf@trop.in \
--to=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=~abcdw/rde-devel@lists.sr.ht \
/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).