From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: GSoC final update Date: Wed, 30 Aug 2017 18:04:58 +0200 Message-ID: <20170830160458.GA2313@jurong> References: <87lgm224xz.fsf@cune.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43268) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dn5UL-00071r-3l for guix-devel@gnu.org; Wed, 30 Aug 2017 12:05:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dn5UF-0007ux-Du for guix-devel@gnu.org; Wed, 30 Aug 2017 12:05:09 -0400 Received: from mailrelay2-2.pub.mailoutpod1-cph3.one.com ([46.30.212.1]:38136) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dn5UF-0007u6-62 for guix-devel@gnu.org; Wed, 30 Aug 2017 12:05:03 -0400 Content-Disposition: inline In-Reply-To: <87lgm224xz.fsf@cune.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Caleb Ristvedt Cc: guix-devel@gnu.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