From: zimoun <zimon.toutoune@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>, guix-devel@gnu.org
Subject: Re: Building, packaging and updating Guix with confidence
Date: Thu, 18 Aug 2022 14:52:08 +0200 [thread overview]
Message-ID: <87edxd7lzb.fsf@gmail.com> (raw)
In-Reply-To: <87let6roxo.fsf@jpoiret.xyz>
Hi Josselin,
Thank you for the clear explanations.
On mer., 06 juil. 2022 at 22:01, Josselin Poiret <dev@jpoiret.xyz> wrote:
[...]
> 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.
Now #53210 [1] is closed, it improves the situation, right? Is it
enough for the C extension you are working on?
1: <https://issues.guix.gnu.org/53210#17>
Cheers,
simon
next prev parent reply other threads:[~2022-08-18 15: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
2022-08-18 12:52 ` zimoun [this message]
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
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=87edxd7lzb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--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 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).