From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Andrew Tropin" <andrew@trop.in>
Subject: Re: guix home
Date: Mon, 15 Mar 2021 16:16:35 -0400 [thread overview]
Message-ID: <831CF304-5776-49F3-90E2-26D145C175F3@lepiller.eu> (raw)
In-Reply-To: <87pn00e4xn.fsf@gnu.org>
Le 15 mars 2021 12:51:16 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi Andrew,
>
>Andrew Tropin <andrew@trop.in> skribis:
>>
>> The question is: do we want and need at all `guix home` to be a part
>of
>> the guix? As for me, the tool seems like a natural addition to guix's
>> declarative configuration management approach and covers the missing
>> piece of user space software management and as I mentioned early
>> upstreaming will allow to make it better integrated with the rest of
>the
>> guix and easier to use for newcommers and casual users, but my
>> perception is obviously biased.
>>
>> Dear maintainers and users, what do you think about making `guix
>home` a
>> part of guix?
>
>I have yet to familiarize myself with ‘guix home’, but overall, I think
>a solution à la ‘guix home’ or guix-home-manager would be a welcome
>addition to Guix.
>
>I agree that these tools are a natural extension of Guix and that it
>makes sense to settle on one approach and make it part of Guix proper.
Obviously I'm not a big fan of having configuration that can be modified after I ran guix home, but I understand this approach sounds less crazy :). I think both approaches have a lot more in common than they diverge, so merging one in guix is just one step away of merging the other :)
Having a read-only home is a fun experiment (that have been going since I started guix-home-manager, so it's definitely possible), but a bit broken, and I keep poking holes for software I can't manage properly.
Also, I had this grand vision of using "extension points" in services, which might be useful to have in Guix. Though I never ended up using them in any meaningful way ^^'.
Merging either of our work will make it more visible and attract more users/contributors, that would be great! If we settle with Andrew's approach, I'd be glad to provide my own services, but I will also probably add something to get back my dear read-only home, because that's the intellectually superior approach, albeit broken ;)
>
>Thanks!
>
>Ludo’.
next prev parent reply other threads:[~2021-03-18 16:24 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
2021-03-15 16:51 ` Ludovic Courtès
2021-03-15 20:16 ` Julien Lepiller [this message]
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=831CF304-5776-49F3-90E2-26D145C175F3@lepiller.eu \
--to=julien@lepiller.eu \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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).