From: Marius Bakke <mbakke@fastmail.com>
To: 38628@debbugs.gnu.org
Subject: bug#38628: Character literals unsupported in source 'snippets'
Date: Sun, 15 Dec 2019 21:27:08 +0100 [thread overview]
Message-ID: <87y2vdcp2b.fsf@devup.no> (raw)
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
Guix,
If you try to use a character literal in a source 'snippet', Guix will
complain about an "unsupported input". I.e. adding the following to the
'hello' package definition:
(snippet '(begin #\!))
Results in:
guix build: error: /home/marius/guix/gnu/packages/base.scm:73:2: package `hello@2.10' has an invalid input: #\!
This is a fairly recent regression. I tracked it down to the following commit:
commit 24ab804ce11fe12ff49cd144a3d9c4bfcf55b41c
Author: Ludovic Courtès <ludo@gnu.org>
Date: Mon Sep 23 22:17:39 2019 +0200
gexp: Catch and report non-self-quoting gexp inputs.
Previously we would, for example, generate build scripts in the store;
when trying to run them, we'd get a 'read' error due to the presence
of #<foo> syntax in there.
* guix/gexp.scm (gexp->sexp)[self-quoting?]: New procedure.
[reference->sexp]: Check whether the argument in a <gexp-input> box is
self-quoting. Raise a '&gexp-input-error' condition if it's not.
* tests/gexp.scm ("lower-gexp, non-self-quoting input"): New test.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2019-12-15 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 20:27 Marius Bakke [this message]
2019-12-15 20:35 ` bug#38628: [PATCH] gexp: Allow character literals in GEXP->SEXP Marius Bakke
2019-12-16 21:51 ` Ludovic Courtès
2019-12-16 21:53 ` Ludovic Courtès
2019-12-18 18:59 ` Marius Bakke
2019-12-18 22:06 ` Marius Bakke
2019-12-19 11:11 ` 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=87y2vdcp2b.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38628@debbugs.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 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).