From: Ricardo Wurmus <rekado@elephly.net>
To: Alex Vong <alexvong1995@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix to participate in the Google Summer of Code
Date: Wed, 21 Feb 2018 10:10:05 +0100 [thread overview]
Message-ID: <87fu5ur9n6.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87vaetnf1d.fsf@gmail.com>
Hi Alex,
>> 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?
The current way to obtain references is through the daemon. In (guix
store) there is a procedure “references” that is used whenever we want
to get a list of references for a store item. But how does the daemon
itself obtain those references in the first place?
“nix/libstore/references.cc” implements a reference scanner and it is
quite similar to how “replace-store-references” in (guix build graft)
works.
So a first step towards an implementation of the reference scanner would
be to liberate “replace-store-references” from its grafting context;
possibly turn it into a higher order function that finds references and
optionally invokes a function when a reference is found. Then it could
be used for grafting as well as for collecting references in the daemon.
But I would recommend to revive the work from the last GSoC first.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-21 10:31 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
2018-02-21 9:10 ` Ricardo Wurmus [this message]
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=87fu5ur9n6.fsf@mdc-berlin.de \
--to=rekado@elephly.net \
--cc=alexvong1995@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).