Hi Josselin, Thank you for the clear explanations.
On mer., 06 juil. 2022 at 22:01, Josselin Poiret <d...@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
