From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sandeep Subramanian Subject: GSoC-2018 - Build daemon rewrite in Scheme Updates Date: Tue, 29 May 2018 11:50:45 +0530 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000bac802056d52382d" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34623) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNXz6-0000Ed-AX for guix-devel@gnu.org; Tue, 29 May 2018 02:19:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNXz5-0003vO-8F for guix-devel@gnu.org; Tue, 29 May 2018 02:19:52 -0400 Received: from mail-qk0-x22e.google.com ([2607:f8b0:400d:c09::22e]:35142) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fNXz5-0003ua-2g for guix-devel@gnu.org; Tue, 29 May 2018 02:19:51 -0400 Received: by mail-qk0-x22e.google.com with SMTP id d130-v6so5258366qkc.2 for ; Mon, 28 May 2018 23:19:50 -0700 (PDT) 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: guix-devel@gnu.org --000000000000bac802056d52382d Content-Type: text/plain; charset="UTF-8" Hi all, It has been two weeks since I started working on the project and I thought I will give you all a quick update regarding it. `build-derivation` is now using `call-with-container` and it seems to work well. `build-derivation` assumes that all the inputs needed for the derivation is already built and ready. As a next step I wanted to try and build the `inputDrvs` if the inputs are missing. I looked through the C++ code to find out how exactly this is done and I have a good understanding of it now. I plan to emulate the behaviour of the C++ code for the entire derivation building pipeline. I spent a lot of time browsing the C++ code base and had to keep going back to it often, since I had trouble keeping the C++ code flow in memory. So, I thought it would be worthwhile to write some detailed notes on the C++ daemon code base that I can refer to while coding. The notes I made can be found here: https://github.com/uniq10/gsoc-guix-notes/blob/master/daemon-notes.md If anybody find any mistakes in those notes kindly let me know. -- uniq10 --000000000000bac802056d52382d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

It has been two weeks since I s= tarted working on
the project and I thought I will give you all a= quick
update regarding it.

`build-deriv= ation` is now using `call-with-container`
and it seems to work we= ll. `build-derivation` assumes
that all the inputs needed for the= derivation is already
built and ready. As a next step I wanted t= o try and build
the `inputDrvs` if the inputs are missing.
<= div>
I looked through the C++ code to find out how exactly=C2= =A0
this is done and I have a good understanding of it now.
=
I plan to emulate the behaviour of the C++ code for=C2=A0
th= e entire derivation building pipeline.

I spent a l= ot of time browsing the C++ code base and had
to keep going back = to it often, since I had trouble keeping=C2=A0
the C++ code flow = in memory. So, I thought it would be=C2=A0
worthwhile to write so= me detailed notes on the C++ daemon
code base that I can refer to= while coding. The notes I made
can be found here:=C2=A0= https://github.com/uniq10/gsoc-guix-notes/blob/master/daemon-notes.md

If anybody find any mistakes in those notes kindly = let me know.

--
uniq10
--000000000000bac802056d52382d--