From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: GSoC final update
Date: Thu, 31 Aug 2017 16:49:24 +0200 [thread overview]
Message-ID: <87r2vrokqz.fsf@gnu.org> (raw)
In-Reply-To: <20170830160458.GA2313@jurong> (Andreas Enge's message of "Wed, 30 Aug 2017 18:04:58 +0200")
Heya,
Andreas Enge <andreas@enge.fr> 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’.
prev parent reply other threads:[~2017-08-31 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:44 GSoC final update Caleb Ristvedt
2017-08-29 8:32 ` Andy Wingo
2017-08-29 10:59 ` Efraim Flashner
2017-08-29 22:52 ` Leo Famulari
2017-08-30 9:50 ` Ludovic Courtès
2017-08-30 12:03 ` Ricardo Wurmus
2017-08-30 16:04 ` Andreas Enge
2017-08-31 14:49 ` Ludovic Courtès [this message]
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=87r2vrokqz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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).