From: Kaz Kylheku <kaz@kylheku.com>
To: 67792@debbugs.gnu.org
Subject: bug#67792: txr: certain string substitution in recipe obsolete.
Date: Mon, 11 Dec 2023 21:36:53 -0800 [thread overview]
Message-ID: <8210feeb4474f274a99584c85b768125@kylheku.com> (raw)
Hi,
In the recipe for txr (in gnu/packages/lisp.scm), this is not
needed any more:
(substitute* "genman.txr"
;; Exit from genman.txr before it tries to write to
;; stdlib/doc-syms.tl, which is anyway kept up to date
;; with each release (and is already compiled to
;; stdlib/doc-syms.tlo when genman.txr is run).
(("^@\\(output \"stdlib/doc-syms\\.tl\"\\).*" line)
(string-append "@(do (exit))\n" line)))))
The doc doc-syms mechanism was removed in 292, so the pattern will not
match.
Cheers ...
next reply other threads:[~2023-12-13 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 5:36 Kaz Kylheku [this message]
2023-12-14 9:53 ` bug#67792: txr: certain string substitution in recipe obsolete Guillaume Le Vaillant
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=8210feeb4474f274a99584c85b768125@kylheku.com \
--to=kaz@kylheku.com \
--cc=67792@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).