From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 53920@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#53920] [PATCH v3] gnu: lesspipe: Update to 2.03.
Date: Mon, 28 Feb 2022 13:31:26 +0100 [thread overview]
Message-ID: <a2eb27fa-3e37-b4ea-b13d-a28ab2324774@crazy-compilers.com> (raw)
In-Reply-To: <87ilszgvpy.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Am 28.02.22 um 10:56 schrieb Nicolas Goaziou:
> Actually, I think it should be the higher-level sexp:
>
> #$(this-package-input "perl-archive-zip")
How can one know, this one to use?
The blog post is more like a historical story, not a tutorial for
converting. It uses both
|#~`("--disable-color" ,(string-append "--with-gawk=" #$gawk)))) |
|and|
|#~(list (string-append "--with-gawk=" #$(this-package-input "gawk"))))) |
|The manual seems to mostly use the former way.|
||||
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2484 bytes --]
next prev parent reply other threads:[~2022-02-28 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:52 [bug#53920] [PATCH] gnu: lesspipe: Update to 2.02 Hartmut Goebel
2022-02-12 9:48 ` Brice Waegeneire
2022-02-20 16:54 ` Hartmut Goebel
2022-02-22 18:42 ` Hartmut Goebel
2022-02-22 9:16 ` [bug#53920] [PATCH v2] " Hartmut Goebel
2022-02-22 18:39 ` [bug#53920] [PATCH v3] gnu: lesspipe: Update to 2.03 Hartmut Goebel
2022-02-27 22:06 ` [bug#53920] [PATCH] gnu: lesspipe: Update to 2.02 Ludovic Courtès
2022-02-27 22:22 ` [bug#53920] [PATCH v3] gnu: lesspipe: Update to 2.03 Maxime Devos
2022-02-28 8:25 ` Hartmut Goebel
2022-02-28 9:56 ` Nicolas Goaziou
2022-02-28 12:31 ` Hartmut Goebel [this message]
2022-02-28 12:50 ` Nicolas Goaziou
2022-03-02 20:52 ` bug#53920: " Hartmut Goebel
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=a2eb27fa-3e37-b4ea-b13d-a28ab2324774@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=53920@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=maximedevos@telenet.be \
/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).