From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Toward 0.2
Date: Fri, 01 Mar 2013 10:15:18 +0100 [thread overview]
Message-ID: <87bob38ord.fsf@gnu.org> (raw)
In-Reply-To: <87ehg0rwfd.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 28 Feb 2013 15:53:19 -0500")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> Remember that (guix build ...) modules must not use Guix modules other
>> than (guix build ...). This is a convention to distinguish between code
>> for the “builder stratum”, and code for the “host stratum”.
>
> OK. But how can I get the location of a package? The needed procedure
> (i.e., 'package-output') is in the host code.
It’s not needed. All that needed is the name of the executable file to wrap.
>> (define* (wrap-program file #:rest variables)
>> ...)
>
> Why do you want to use '#:rest' here? The purpose of 'wrap-program' is
> to export some variables.
For the case where there are have several variables you want to set.
>> export CERT_PATH=$CERT_PATH${CERT_PATH:+:}:/nix/.../share/certs
>
> Could you explain the "$CERT_PATH${CERT_PATH:+:}" part?
The :+ part is to add a colon if and only if $CERT_PATH is non-empty
(info "(bash) Shell Parameter Expansion").
Otherwise you could end up with a value like “:/foo”, but the first
empty element (before the colon) is usually equivalent to “.”, and we
don’t want that.
>> Perhaps the separator string could be optional.
>
> Is it possible to make it optional without creating a separate clause?
No, you’d need an additional clause.
> +(define (wrap-program prog varlst)
> + "Copy PROG to .PROG-real and make PROG a wrapper."
Could you document what the wrapper does, and what the grammar of
‘varlst’ (rather call it ‘vars’) is?
> + (define (export-envvar lst)
‘export-variable’, rather.
> + (define (separate lst delim)
You ‘string-join’ instead:
(string-join '("a" "b") ":")
=> "a:b"
> + ;; TODO: Make SEP optional.
> + (match lst
> + ((var sep '= rest)
> + (format #f "export ~a=\"~a\""
> + var (separate rest sep)))
> +
> + ((var sep 'prefix rest)
> + (format #f "export ~a=\"~a~a${~a~a+~a}$~a\""
> + var (separate rest sep) sep var sep sep var))
> +
> + ((var sep 'suffix rest)
> + (format #f "export ~a=\"$~a${~a~a+~a}~a~a\""
> + var var var sep sep sep (separate rest sep)))))
Good (please indent like other uses of ‘match’ in this file).
> + ;; XXX: Use an absolute filename; remove '-real'.
> + (format #f "#!~a~%~aexec ./.~a-real~%"
> + (which "bash")
> +
> + (fold-right (lambda (x acc)
> + (string-append x "\n" acc))
> + ""
> + (map export-envvar varlst))
string-join
> + prog)) ; XXX: use a real program instead
Just (canonicalize-path prog).
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-03-01 9:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 15:10 Toward 0.2 Ludovic Courtès
2013-02-18 1:58 ` Nikita Karetnikov
2013-02-18 10:26 ` Ludovic Courtès
2013-02-20 0:39 ` Nikita Karetnikov
2013-02-20 11:28 ` Ludovic Courtès
2013-02-21 17:36 ` Nikita Karetnikov
2013-02-22 14:31 ` Ludovic Courtès
2013-02-26 10:43 ` Nikita Karetnikov
2013-02-26 16:51 ` Mark H Weaver
2013-02-26 19:14 ` Ludovic Courtès
2013-02-28 20:53 ` Nikita Karetnikov
2013-03-01 9:15 ` Ludovic Courtès [this message]
2013-03-01 15:01 ` Nikita Karetnikov
2013-03-01 17:28 ` Ludovic Courtès
2013-03-02 20:17 ` Nikita Karetnikov
2013-03-02 21:30 ` Ludovic Courtès
2013-03-03 12:52 ` [PATCH] utils: Add 'wrap-program'. (was: Toward 0.2) Nikita Karetnikov
2013-03-03 21:29 ` [PATCH] utils: Add 'wrap-program' Ludovic Courtès
2013-03-03 23:11 ` Nikita Karetnikov
2013-03-04 10:08 ` Ludovic Courtès
2013-02-20 9:00 ` Toward 0.2 Andreas Enge
2013-04-15 21:59 ` Ludovic Courtès
2013-04-29 21:32 ` Ludovic Courtès
2013-05-11 20:41 ` 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=87bob38ord.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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.