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: Tue, 03 Jan 2017 00:10:49 +0100 [thread overview]
Message-ID: <878tqt6osm.fsf@gnu.org> (raw)
In-Reply-To: <9a3f6d70-e24f-2273-4599-94ef0cb05763@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 31 Dec 2016 13:56:23 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 31.12.2016 um 00:42 schrieb Ludovic Courtès:
>> Where does that string you want to build go to?
>
> As I already wrote in my initial mail, I need to reference the actual
> package output's path in some config-file within a system definition
> (e.g. gnu/system/examples/nginx.tmpl).
>
> So assume gnu/system/examples/nginx.tmpl to be:
>
> (use-modules (gnu))
> (use-package-modules networking web)
> (define NGINX (package-output (open-connection) nginx))
> (define TEST (string-append NGINX "/bin/nginxctl"))
>
> If "package-output" is not the correct solution, please tell me the
> correct one.
I think the discussion drifted a bit. Your initial message mentioned
this use case:
(nginx-service #:vhost-list
(list (nginx-vhost-configuration
(root (string-append nginx "/share/nginx/html"))
(https-port #f)
(ssl-certificate #f)
(ssl-certificate-key #f))))
I explained back in November what I think should be done to fix this (as
in: allow you to write (file-append nginx "/share/nginx/html") above):
https://lists.gnu.org/archive/html/guix-devel/2016-11/msg00161.html
Julien submitted a patch just before the holidays that nobody has taken
the time to review yet. I’ll see if I can look at it tomorrow, but help
is always welcome!
Ludo’.
prev parent reply other threads:[~2017-01-02 23:10 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
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 [this message]
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=878tqt6osm.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).