unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "(" <paren@disroot.org>
To: "(" <paren@disroot.org>
Cc: Christian Miller <miller.christian@proton.me>, guix-devel@gnu.org
Subject: Re: Guix system init but for guix home
Date: Tue, 08 Aug 2023 13:53:47 +0100	[thread overview]
Message-ID: <87bkfh1ylq.fsf@disroot.org> (raw)
In-Reply-To: <87pm42oamr.fsf@disroot.org>


"(" <paren@disroot.org> writes:

> Christian Miller <miller.christian@proton.me> writes:
>> Basically my idea would be, that I am on the live ISO and run guix system init
>> [...] and after that I would run guix home init home.scm /mnt or something like
>> that.  Now if I reboot in to the actual system, I have my complete setup with
>> EXWM and Emacs completely configured and ready to go.
>
> Something that would cover this use case be a HOME-ENVIRONMENT field for
> user-accounts in /etc/config.scm:
>
>   (user-account
>    (name "paren")
>    ...
>    (home-environment
>     ...))
>
> which could either be a file-like that evaluates to a Scheme file that
> returns a HOME-ENVIRONMENT object, or a HOME-ENVIRONMENT by itself:
>
>   ;; with local-file
>   (home-environment
>    (local-file
>     (string-append (dirname (get-current-filename))
>                    "/home-paren.scm")))
>
>   ;; with home-environment
>   (home-environment
>    (home-environment
>     (services (cons* ...))
>     (packages (list ...))))
>
>   -- (

OP accidentally sent replies without CCing the mailing list, so:

Christian Miller:
> I like it, since now it is just the default command for initializing Guix.
>
> With that change, would that also mean that someone doesn't need to run "guix
> home reconfigure home.scm", since the person could just run "guix system
> reconfigure system.scm" after a "guix pull", if the person wants to update the
> whole system and the home packages like in my case?

me:
> Exactly.

Christian Miller:
> I like that.  Makes stuff easier for people like me that use both.
>
> I also replied to you directly.  I should have replied to all, so the system
> detects it as well.  Just to be sure, is that correct?
>
> How would we now add that stuff, so others could see those emails as
> well?

me:
> You'd have to resend it with the To: address changed and possibly also
> In-Reply-To: modified as well.  I guess you could just use 'reply all'
> in your mail client and then remove my address from the To: field.

Christian Miller:
> Hi,
>
> it seems that my mail client can only do this for one message, but we had
> several messages.  Should I begin with my initial message and we go through it
> again, or could you send all at once?

me:
> I'll send a compilation of all the messages as a reply to the original
> post.

  -- (


  reply	other threads:[~2023-08-08 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 19:12 Guix system init but for guix home Christian Miller
2023-08-04 19:40 ` (
2023-08-08 12:53   ` ( [this message]
2023-08-13  5:45   ` 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=87bkfh1ylq.fsf@disroot.org \
    --to=paren@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=miller.christian@proton.me \
    /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).