From: Joshua Branson <jbranso@dismail.de>
To: Andrew Tropin <andrew@trop.in>
Cc: guix-devel@gnu.org
Subject: Re: guix home
Date: Sun, 14 Mar 2021 11:46:55 -0400 [thread overview]
Message-ID: <87pn01agb4.fsf@dismail.de> (raw)
In-Reply-To: <878s6u2pco.fsf@trop.in> (Andrew Tropin's message of "Thu, 11 Mar 2021 09:09:43 +0300")
Andrew Tropin <andrew@trop.in> writes:
> Hi guix!
>
> There is an implementation of `guix home` subcommand, which behaves
> similar to `guix system`, allowing declaratively manage applications and
> their configurations, but for a particular user, not the whole OS:
> https://git.sr.ht/~abcdw/rde/tree/master/item/gnu
Thanks for sharing this! And it's on sourcehut! Very rock star of you!
>
> For now I personally manage just a few applications on my system and it
> seems that everything works as expected, but I plan to migrate all the
> "dotfiles" to it in nearest future. AFAIK, some people succesfully use
> it on other GNU/Linux distributions.
That's awesome!
>
> * Alternative solutions
> In contrast to guix-home-manager, `guix home` doesn't introduce any too
For those interested the guix-home-manager is here:
https://framagit.org/tyreunom/guix-home-manager
> innovative approaches (those ideas are cool, but in some use cases are
> too radical), `guix home` uses the same extension mechanism [fn:1] as
> guix system services and doesn't require to make HOME read-only. Thus,
> it's possible to start using `guix home` gradually, along with other
> tools and workflows (stow, guix package, chezmoi, yadm, etc).
Honestly, this is why I haven't tried the guix-home-manager. I didn't
want to make /home read only. That sounded hard to switch to. I'll
have to give your guix home command a try! It sounds easy!
> * Future steps
> `guix home` still under active development, but already complete enough
> for exloration and early adoption. There is no any documentation yet,
> because things were changing often and probably will change one more
> time during comming cleanup, however there were few video streams,
> explaining internals of `guix home`:
> mpv https://youtu.be/t3zRzQnarUI
> mpv https://youtu.be/4lJaVzxO_Bs
> mpv https://youtu.be/ZRQtCvo8MoM
>
> 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.
I believe the goal is to eventually merge guix-home-manager (or
something like it) into guix. (I'm more of a guix documentation guy, so
perhaps a guix developer can better answer this).
> --
> Best regards,
> Andrew Tropin
I'm going to remember that name. Andrew's going places!
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-03-14 15:47 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 [this message]
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
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=87pn01agb4.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=andrew@trop.in \
--cc=guix-devel@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).