help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Design decision behind inputs/native-inputs/propagated-inputs


From: Ludovic Courtès
Subject: Re: Design decision behind inputs/native-inputs/propagated-inputs
Date: Sat, 23 Jan 2016 22:12:58 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Steven Allen <address@hidden> skribis:

> Can anyone tell me what's going on here or point me to the relevant
> documentation? Specifically, why does the daemon (assuming guix-daemon)
> need to see what store items the package refers to?

At the end of a build, guix-daemon scans all the produced file in search
of references to other store items.  It then records those run-time
references (so a subset of the build-time dependencies) in the
/var/guix/db/db.sqlite database, which can be queried with
‘guix gc --references’.

Scanning is also made from ‘registerOutputs’ in build.cc.

For background, see Eelco Dolstra’s thesis at
<http://nixos.org/~eelco/pubs/phd-thesis.pdf>.

HTH!

Ludo’.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]