From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: guix-devel@gnu.org, guix-patches@gnu.org
Subject: Re: Merging wip-guix-home to master
Date: Thu, 23 Sep 2021 22:45:45 +0200 [thread overview]
Message-ID: <87h7eb81hi.fsf@gnu.org> (raw)
In-Reply-To: <87sfxvehyf.fsf@trop.in> (Andrew Tropin's message of "Thu, 23 Sep 2021 12:53:28 +0300")
Hi,
Andrew Tropin <andrew@trop.in> skribis:
> 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.
Yay! I’d like to take another look (I know I’ve been terribly MIA,
apologies!), and I hope other folks familiar with Guix System can
comment as well.
> 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.
I know it can be annoying to existing Guix Home users, but I’d prefer
not to carry pre-merge baggage; that is, we’d just rename and not
provide those modules under their former names at all.
> 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.
Do you have ideas of a possible testing strategy?
We should be able to test at least the CLI, either arranging to avoid
large builds (as in tests/guix-build.sh) or talking to the “real”
guix-daemon (as in tests/guix-pack-relocatable.sh) if we’re going to
need packages.
It’d be great to have this part ready soonish.
The way I see it, in 1.4 (2.0?), we’d mark Guix Home as a “technology
preview” in the manual with a prominent note. That will allow us to get
feedback from new users and to fine-tune code correspondingly, and
that’ll make it clear to users that things are still subject to change.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-23 20:46 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 [this message]
2021-09-24 7:43 ` Andrew Tropin
2021-09-24 13:38 ` Xinglu Chen
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=87h7eb81hi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=guix-patches@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).