all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:31:15 +0100	[thread overview]
Message-ID: <87oa0859lo.fsf@gnu.org> (raw)
In-Reply-To: <42bb5a6c-6a7c-c348-d9d0-da83805cdffe@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 19 Dec 2016 12:05:04 +0100")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 19.12.2016 um 10:47 schrieb Ludovic Courtès:
>> 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")
>
> Thanks for the explanation (which to be frank would take me some time to
> understand).
>
> Please reread you answer from the point of view of an administrator or
> somebody else who is not a Scheme programmer. Somebody who just wants to
> get some system up an running. He would answer like this:
>
>     Parton? What? "string-valued gexp", "staging context"? I do not
>     care. I simply want to get the path to a file within a package.
>
> Whatever you write above may be correct and may be understandable for
> every Scheme programmer. But this is discouraging for everybody who does
> not want to become a Scheme expert for administering his/her systems.
>
> I already wasted about an hour just to try to get this path! This is crap!

I agree!  The first two lines were all you wanted to know; the rest was
for you as someone who contributes to Scheme—I would not give that
explanation to someone who’s just trying to get nginx up and running.

As for the specifics of why ‘nginx-configuration’ makes this use case
complicated, I think we discussed it on guix-devel before, and there was
probably an action item, but “someone” just needs to make it happen or
at least to keep track of it.

HTH!  :-)

Ludo’.

  reply	other threads:[~2016-12-19 13:31 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa0859lo.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.