From: Maxime Devos <maximedevos@telenet.be>
To: Efraim Flashner <efraim@flashner.co.il>, 54123@debbugs.gnu.org
Subject: [bug#54123] [PATCH 2/5] gnu: Add go-github-com-niemeyer-pretty.
Date: Wed, 23 Feb 2022 13:39:00 +0100 [thread overview]
Message-ID: <3e005ac0e0c41ec31ca0b3edb44ce63ef1770e62.camel@telenet.be> (raw)
In-Reply-To: <98ccc56c6c203acd07dcb8ec0a81c0a39db622b9.1645611835.git.efraim@flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Efraim Flashner schreef op wo 23-02-2022 om 12:29 [+0200]:
> + (arguments
> + '(#:import-path "github.com/niemeyer/pretty"
> + #:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'patch-source
> + (lambda _
> + ;; https://github.com/kr/pretty/pull/66
> + (substitute* "src/github.com/niemeyer/pretty/formatter.go"
> + (("string\\(i\\)") "string(rune(i))")))))))
The 'patches' and 'snippet' fields of 'origin' are for patching
source code. While patching in a phase works, an origin snippet
seems a more natural place to me.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-23 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:24 [bug#54123] [PATCH 0/5] some golang packages Efraim Flashner
2022-02-23 10:29 ` [bug#54123] [PATCH 1/5] gnu: Add go-github-com-xdg-go-stringprep Efraim Flashner
2022-03-06 10:26 ` bug#54123: " Efraim Flashner
2022-02-23 10:29 ` [bug#54123] [PATCH 2/5] gnu: Add go-github-com-niemeyer-pretty Efraim Flashner
2022-02-23 12:39 ` Maxime Devos [this message]
2022-02-23 10:29 ` [bug#54123] [PATCH 3/5] gnu: Add go-github-com-docker-go-units Efraim Flashner
2022-02-23 10:29 ` [bug#54123] [PATCH 4/5] gnu: Add go-github-com-xdg-go-pbkdf2 Efraim Flashner
2022-02-23 10:29 ` [bug#54123] [PATCH 5/5] gnu: Add go-github-com-xdg-go-scram Efraim Flashner
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=3e005ac0e0c41ec31ca0b3edb44ce63ef1770e62.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54123@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.