[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSoC final update
From: |
Ludovic Courtès |
Subject: |
Re: GSoC final update |
Date: |
Thu, 31 Aug 2017 16:49:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Heya,
Andreas Enge <address@hidden> skribis:
> I have a probably naïve question, since I did not follow the project closely:
> Instead of an all-or-nothing outcome, success or failure, merge or bit rot,
> would it be possible to set up an incremental update path?
> Use some of your scheme code to replace part of the C++ daemon?
> Maybe write a high-level scheme engine that shells out to C++ functions in
> the current daemon, that could gradually be replaced by chunks of your code?
I like this idea. One of the first things reepca worked on was writing
a replacement for the ‘guix-register’ C++ program in Scheme, which also
provides the foundation for everything else on that branch.
I think we should be able to merge this bit independently of the rest,
as a first step.
It requires care, but that’s definitely something we should look into.
Thanks,
Ludo’.
- GSoC final update, Caleb Ristvedt, 2017/08/29
- Re: GSoC final update, Andy Wingo, 2017/08/29
- Re: GSoC final update, Efraim Flashner, 2017/08/29
- Re: GSoC final update, Leo Famulari, 2017/08/29
- Re: GSoC final update, Ludovic Courtès, 2017/08/30
- Re: GSoC final update, Ricardo Wurmus, 2017/08/30
- Re: GSoC final update, Andreas Enge, 2017/08/30
- Re: GSoC final update,
Ludovic Courtès <=