unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: Andrew Tropin <andrew@trop.in>, Oleg Pykhalov <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Merging wip-guix-home to master
Date: Fri, 24 Sep 2021 15:38:49 +0200	[thread overview]
Message-ID: <87sfxujdp2.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87sfxvehyf.fsf@trop.in>

[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]

On Thu, Sep 23 2021, Andrew Tropin wrote:

> The core part of Guix Home project has been moved from rde
> repository[fn:1] to wip-guix-home branch of guix repository.
>
> I'm about a week on wip-guix-home branch completely and Guix Home works
> fine.  There are no any major issues on rde-devel and guix-devel mailing
> lists and it seems that branch is ready to be merged.
>
> My guix describe looks like:
> --8<---------------cut here---------------start------------->8---
> Generation 114	Sep 17 2021 13:33:55	(current)
>   rde 31f8003
>     repository URL: https://git.sr.ht/~abcdw/rde
>     branch: without-guix-home
>     commit: 31f800353a781cef25fc80c05ad824a068a049c8
>   guix a2324d8
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: wip-guix-home
>     commit: a2324d8b56eabf8117bca220a507cc791edffd2e
> --8<---------------cut here---------------end--------------->8---
>
>
> There is a discussion[fn:2] on moving home services to (gnu services
> ...)  modules, which is likely to happen, but it's possible to do the
> migration relatively painless by re-exporting necessary symbols in
> (gnu home-services ...) at first and removing them completely later.
>
> Another important part of the work related to Guix Home project is
> covering related modules and cli with tests, but it can be done in
> parallel and is not a blocker for merging.

I noticed that the ‘guix home import’ subcommand is included, but I
think it needs more thought and feedback from people before it makes its
way into ‘master’; it also seems to lack documentation.

I just realized that it generates the following service declaration

--8<---------------cut here---------------start------------->8---
(service
 home-bash-service-type
 (home-bash-configuration
  (bashrc
   (list (slurp-file-gexp
          (local-file "/home/yoctocell/.bashrc"))))))
--8<---------------cut here---------------end--------------->8---

but when running ‘guix home reconfigure’, the ~/.bashrc file will be
moved, so when running ‘guix home reconfigure’ for the second time, it
would read the ~/.bashrc which is itself a symlink to a file the store.
‘guix home import’ clearly isn’t in a usable state as of right now…


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  parent reply	other threads:[~2021-09-24 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  9:53 Merging wip-guix-home to master Andrew Tropin
2021-09-23 15:27 ` Katherine Cox-Buday
2021-09-24  7:12   ` Andrew Tropin
2021-09-23 20:45 ` Ludovic Courtès
2021-09-24  7:43   ` Andrew Tropin
2021-09-24 13:38 ` Xinglu Chen [this message]
2021-09-28 10:14   ` Andrew Tropin
2021-09-29 11:39     ` Xinglu Chen
2021-09-29 14:15       ` Katherine Cox-Buday
2021-09-29 15:02         ` Xinglu Chen
2021-09-30  6:11       ` Andrew Tropin
2021-09-28 12:43   ` Ludovic Courtès
2021-09-28 15:23     ` Xinglu Chen

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=87sfxujdp2.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=andrew@trop.in \
    --cc=go.wigust@gmail.com \
    --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).