unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix to participate in the Google Summer of Code
Date: Tue, 20 Feb 2018 00:02:38 +0800	[thread overview]
Message-ID: <87vaetnf1d.fsf@gmail.com> (raw)
In-Reply-To: <874lmey4ki.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 18 Feb 2018 11:28:45 +0100")

Hello Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Alex,
>
>> I want to be a student this year since this will be my final chance (I
>> am graduating this year). I look at the libreplanet page and I think
>> only the build daemon project is suitable for me since I don't have
>> knowledge in networking. Is it possible for me to work on last-year
>> Bournish project?
>
> The Bournish project is poorly defined now that gash exists, a Bash
> interpreter written in Guile.  It wouldn’t be a lot of work to integrate
> gash into Guix and replace Bournish; in fact I wanted to do this myself
> in a few weeks.
>
OK, so we already have a working Bash interpreter written in Guile. It
makes sense to drop the old plan then.

> I’m afraid that the Bournish project would no longer be suitable for
> GSoC, and that’s why it had been removed from the list of project ideas.
>
I see. So this is why I think I have seen it before. It was on the list
of idea but then get removed.

> The guix-daemon project is larger but also much more useful to us.
> Garbage collection in the context of Guix is not very difficult to
> understand.  The garbage collector may remove any item that has zero
> users; the link count on a store item is indicative of the number of
> users that item has.  For garbage collection you essentially go through
> all items and check if the link count is zero.
>
I will join the guix-daemon project then. My understading is that the
garbage collector also uses info from 'list-runtime-roots', right? So
together we have registered roots and runtime roots.

> The reference scanner is already implemented in the form of grafts.  The
> code opens each file and searches efficiently for store references.
>
Does this mean we have procedure to do a single find-reference and the
remaining work is to build a recursive find-reference?

> For that project it is best to spend a day or two browsing the existing
> Guile sources and noting the many things that already implement large
> parts of the daemon features.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net

Cheers,
Alex

  reply	other threads:[~2018-02-19 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 23:47 Guix to participate in the Google Summer of Code Ludovic Courtès
2018-02-18  7:23 ` Alex Vong
2018-02-18 10:28   ` Ricardo Wurmus
2018-02-19 16:02     ` Alex Vong [this message]
2018-02-21  9:10       ` Ricardo Wurmus
2018-02-21  6:23     ` Chris Marusich
2018-02-21  8:25       ` Ricardo Wurmus

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=87vaetnf1d.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).