From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix@gnu.org
Subject: Re: string-append plus package
Date: Mon, 19 Dec 2016 10:47:26 +0100 [thread overview]
Message-ID: <87h9608d3l.fsf@gnu.org> (raw)
In-Reply-To: <d74b030d-d74d-3ece-f30e-13e2a557a972@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 19 Dec 2016 01:13:10 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 08.12.2016 um 20:56 schrieb Leo Famulari:
>>> Here is the service-definition I use:
>>>
>>> (nginx-service #:vhost-list
>>> (list (nginx-vhost-configuration
>>> (root (string-append nginx "/share/nginx/html"))
>> I believe that file-append is intended for this use case.
>
> Maybe, but I can't get it to work. This minimal system declarision fails
> with "In procedure string-append: Wrong type (expecting string):
> #<<file-append> base: #<package nginx@1.11.6 gnu/packages/web.scm:126
> 2a236c0> suffix: ("/")>"
>
> (use-modules (gnu))
> (use-service-modules networking web)
> (define NGINX (file-append nginx "/"))
> (define TEST (string-append NGINX ""))
The result of ‘file-append’ is not a string, but ‘string-append’ expects
two strings, hence the error.
‘file-append’ returns a “string-valued gexp”. This is to say that, in a
staging context, it will produce a string. For example:
(scheme-file "foo" #~(foo bar #$(file-append nginx "/foo/bar")))
leads to a file “foo” containing:
(foo bar "/gnu/store/…-nginx-1.2.3/foo/bar")
HTH!
Ludo’.
next prev parent reply other threads:[~2016-12-19 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 17:01 string-append plus package Hartmut Goebel
2016-12-08 17:28 ` Thompson, David
2016-12-08 17:46 ` Hartmut Goebel
2016-12-08 17:47 ` Thompson, David
2016-12-08 19:56 ` Leo Famulari
2016-12-19 0:13 ` Hartmut Goebel
2016-12-19 9:47 ` Ludovic Courtès [this message]
2016-12-19 11:05 ` Hartmut Goebel
2016-12-19 13:31 ` Ludovic Courtès
2017-01-01 15:34 ` Hartmut Goebel
2017-01-02 23:05 ` Ludovic Courtès
2016-12-29 10:57 ` Hartmut Goebel
2016-12-29 13:06 ` Mathieu Lirzin
2016-12-29 14:21 ` Hartmut Goebel
2016-12-30 23:42 ` Ludovic Courtès
2016-12-31 12:56 ` Hartmut Goebel
2017-01-02 23:10 ` 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=87h9608d3l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@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.
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).