From: Sandeep Subramanian <sandeepsubramanian94@gmail.com>
To: guix-devel@gnu.org
Subject: GSoC-2018 - Build daemon rewrite in Scheme Updates
Date: Tue, 29 May 2018 11:50:45 +0530 [thread overview]
Message-ID: <CAEMWfy=+nq__SHDiFx8gc3jrk7VNv06vRKFQsAyaERs+84xseQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1470 bytes --]
next reply other threads:[~2018-05-29 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 6:20 Sandeep Subramanian [this message]
2018-05-29 19:52 ` GSoC-2018 - Build daemon rewrite in Scheme Updates Ludovic Courtès
2018-06-06 17:03 ` 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='CAEMWfy=+nq__SHDiFx8gc3jrk7VNv06vRKFQsAyaERs+84xseQ@mail.gmail.com' \
--to=sandeepsubramanian94@gmail.com \
--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).