unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: guix-devel@gnu.org
Subject: Re: GSoC final update
Date: Wed, 30 Aug 2017 18:04:58 +0200	[thread overview]
Message-ID: <20170830160458.GA2313@jurong> (raw)
In-Reply-To: <87lgm224xz.fsf@cune.org>

Hello Caleb,

On Tue, Aug 29, 2017 at 02:44:56AM -0500, Caleb Ristvedt wrote:
> Currently nothing has been merged - I don't think it's in a fit state to
> be merged presently. I intend to continue working on this as time
> allows.  School started last week, though, and it's kept me quite busy
> so far.
> 
> The code so far can be found at the guile-daemon branch on Savannah.

hopefully you will find some time to continue working on the project!
It would definitely be great to end up with a daemon written in Guile
at some point in time.

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?

If this is nonsense, please do not hesitate, you or other specialists of
the topic, to call it so ;-)

Cheers,

Andreas

  parent reply	other threads:[~2017-08-30 16:05 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 [this message]
2017-08-31 14:49   ` Ludovic Courtès

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=20170830160458.GA2313@jurong \
    --to=andreas@enge.fr \
    --cc=caleb.ristvedt@cune.org \
    --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).