me/guix
Archived
1
0
Fork 0
Code Activity

doc: Mention Kiselyov's work on "staging".

Browse source 
* doc/guix.texi (G-Expressions): Mention Oleg's work on "staging" in
  footnote.
This commit is contained in:
Ludovic Courtès 2014-05-08 21:50:53 +02:00
parent 03178aec1d
commit ef4ab0a4c5
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/guix.texi
View file

@ -1995,10 +1995,14 @@ build the derivations; they are run by the daemon in a container
It should come as no surprise that we like to write those build actions It should come as no surprise that we like to write those build actions
in Scheme. When we do that, we end up with two @dfn{strata} of Scheme in Scheme. When we do that, we end up with two @dfn{strata} of Scheme
code@footnote{The term @dfn{stratum} in this context was coined by code@footnote{The term @dfn{stratum} in this context was coined by
Manuel Serrano et al.@: in the context of their work on Hop.}: the Manuel Serrano et al.@: in the context of their work on Hop. Oleg
``host code''---code that defines packages, talks to the daemon, Kiselyov, who has written insightful
etc.---and the ``build code''---code that actually performs build @url{http://okmij.org/ftp/meta-programming/#meta-scheme, essays and code
actions, such as making directories, invoking @command{make}, etc. on this topic}, refers to this kind of code generation as
@dfn{staging}.}: the ``host code''---code that defines packages, talks
to the daemon, etc.---and the ``build code''---code that actually
performs build actions, such as making directories, invoking
@command{make}, etc.
To describe a derivation and its build actions, one typically needs to To describe a derivation and its build actions, one typically needs to
embed build code inside host code. It boils down to manipulating build embed build code inside host code. It boils down to manipulating build