From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Building, packaging and updating Guix with confidence
Date: Mon, 18 Jul 2022 13:03:22 +0200 [thread overview]
Message-ID: <87tu7e1y4l.fsf@gnu.org> (raw)
In-Reply-To: <87let6roxo.fsf@jpoiret.xyz> (Josselin Poiret's message of "Wed, 06 Jul 2022 22:01:07 +0200")
Hi!
I’m late to the party, but I like your thoughtful message.
Josselin Poiret <dev@jpoiret.xyz> skribis:
> What I personally think, is that we should rationalize the way we
> interact with Guix source: a running Guix should always be able to hold
> a reference to its source. The guix package or future equivalent
> (ie. good for internal consumption) should always refer to that same
> source, but that will also require factoring the daemon (and extensions)
> out of the repository, so that the C code doesn't get compiled again on
> every unrelated commit. Finally, and I think this is the most
> challenging one, we should try to keep the differences between a) and c)
> to the minimum, meaning that one way of building has to go. This is a
> big change, conceptually and technically, and I understand that this
> might be way more complicated that we'd like, but I think this needs to
> be done at some point.
I definitely agree.
I’d summarize things a bit differently:
1. We have two build systems for the same software: the GNU build
system and (guix self).
2. We have that crazy ‘guix’ package snapshot, which causes the
problems you mentioned.
Both contribute to a poor developer experience, but I believe they can
be addressed separately.
It’s not clear that #1 is much of a problem in practice. Someone who
contributes to Guix may have to touch gnu/local.mk, but that rarely goes
beyond that. It’s annoying, but it’s not clear to me that it’s a
showstopper for newcomers.
One thing that would be nice is getting rid of ‘guix-daemon’ and
replacing it with a pure Scheme/Guix way of building the C++ code that
(guix self) would use.
#2 is the main issue to me. There’s an open bug about it¹, which I’d
like to address at least in the context of the installer.
Thanks,
Ludo’.
¹ https://issues.guix.gnu.org/53210
next prev parent reply other threads:[~2022-07-18 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 20:01 Building, packaging and updating Guix with confidence Josselin Poiret
2022-07-07 12:06 ` Zhu Zihao
2022-07-07 14:34 ` Josselin Poiret
2022-07-17 16:52 ` bokr
2022-07-21 16:10 ` Josselin Poiret
2022-07-21 16:18 ` Maxime Devos
2022-07-26 1:09 ` Bengt Richter
2022-08-18 13:19 ` zimoun
2022-07-18 11:03 ` Ludovic Courtès [this message]
2022-08-18 12:52 ` zimoun
2022-08-19 10:21 ` Josselin Poiret
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu7e1y4l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dev@jpoiret.xyz \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.