unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 34574@debbugs.gnu.org
Subject: bug#34574: Confusing manual entry for gexp->file
Date: Wed, 06 Mar 2019 14:17:49 +0100	[thread overview]
Message-ID: <871s3kjg5e.fsf@gnu.org> (raw)
In-Reply-To: <20190219162120.7evs2ynhhdksyq2d@pelzflorian.localdomain> (pelzflorian's message of "Tue, 19 Feb 2019 17:21:20 +0100")

Hi Florian,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> The Guix manual contains the following description of gexp->file:
>
>  -- Monadic Procedure: gexp->file NAME EXP [#:set-load-path? #t]
>           [#:module-path %load-path]  [#:splice? #f]  [#:guile
>      (default-guile)] Return a derivation that builds a file NAME
>      containing EXP. When SPLICE? is true, EXP is considered to be a
>      list of expressions that will be spliced in the resulting file.
>
>      When SET-LOAD-PATH? is true, emit code in the resulting file to set
>      ‘%load-path’ and ‘%load-compiled-path’ to honor EXP’s imported
>      modules. Look up EXP’s modules in MODULE-PATH.
>
>      The resulting file holds references to all the dependencies of EXP
>      or a subset thereof.
>
> I do not understand this last sentence.  How can it be a subset?  A
> subset of what?  Can this be explained more clearly or removed?

It can be a subset of the references of EXP because, when a build
completes, the daemon scan the output(s) to determine the set of
residual references.  That’s the difference between build-time and
run-time dependencies.

For instance, ‘sed’ depends on ‘gcc’ and ‘gcc:lib’ at build time, but
its output depends only on ‘gcc:lib’.

Does that make sense?

Ludo’.

  reply	other threads:[~2019-03-06 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 16:21 bug#34574: Confusing manual entry for gexp->file pelzflorian (Florian Pelz)
2019-03-06 13:17 ` Ludovic Courtès [this message]
2019-03-06 18:35   ` pelzflorian (Florian Pelz)
2019-03-08 10:48     ` 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=871s3kjg5e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34574@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).