From: Maxime Devos <maximedevos@telenet.be>
To: SeerLite <seerlite@nixnet.email>, 54221@debbugs.gnu.org
Subject: [bug#54221] [PATCH 3/4] gnu: vim: Update package style.
Date: Wed, 02 Mar 2022 19:29:47 +0100 [thread overview]
Message-ID: <6002b969ed2f353fef0e8fa87d4fc7d01d3344fa.camel@telenet.be> (raw)
In-Reply-To: <da08c31cbea9bc194bf1eea68c3c532e28628310.1646227054.git.seerlite@nixnet.email>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
SeerLite via Guix-patches via schreef op wo 02-03-2022 om 10:17 [-
0300]:
> + (lambda* (#:key inputs #:allow-other-keys)
> + [this [bracketed line] seems irrelevant for my comment]
> + (substitute* '("src/testdir/Makefile"
> + "src/testdir/test_normal.vim"
> + "src/testdir/test_popupwin.vim"
> + "src/testdir/test_shell.vim"
> + "src/testdir/test_system.vim"
> + "src/testdir/test_terminal.vim"
> + "src/testdir/test_terminal2.vim")
> + (("/bin/sh") (search-input-file inputs "bin/sh")))
> + (substitute* "src/testdir/test_autocmd.vim"
> + (("/bin/kill") (search-input-file inputs "bin/kill")))))
This is test stuff, and these binaries do not seem to be present in
'inputs', they would be in the implicit 'native-inputs', so these would
need to search in '(or native-inputs inputs)' instead of 'inputs' to
avoid &search-path exceptions when cross-compiling:
(substitute* '("src/testdir/...")
(("/bin/sh") (search-input-file (or native-inputs inputs) "bin/sh")))
Or simpler, there's a procedure for looking for 'bin/TOOL' in native-
inputs: 'which'!
;; the original code!
(substitute* '("src/testdir/...")
(("/bin/sh") (which "sh")))
Why the change from 'which' to 'search-input-file'?
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-03-02 18:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 13:11 [bug#54221] [PATCH 0/4] vim: Detect plugins via search paths SeerLite via Guix-patches via
2022-03-02 13:17 ` [bug#54221] [PATCH 1/4] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2022-03-02 13:17 ` [bug#54221] [PATCH 2/4] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-03-02 18:30 ` Maxime Devos
2022-03-02 13:17 ` [bug#54221] [PATCH 3/4] gnu: vim: Update package style SeerLite via Guix-patches via
2022-03-02 18:25 ` Maxime Devos
2022-03-02 18:29 ` Maxime Devos [this message]
2022-03-03 16:49 ` SeerLite via Guix-patches via
2022-03-03 17:46 ` Maxime Devos
2022-03-02 18:35 ` Maxime Devos
2022-03-03 17:40 ` SeerLite via Guix-patches via
2022-03-16 14:16 ` [bug#54221] [PATCH 0/4] vim: Detect plugins via search paths Ludovic Courtès
2022-05-13 2:34 ` seerlite--- via Guix-patches via
2022-05-19 1:11 ` [bug#54221] [PATCH v4 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-03-02 13:17 ` [bug#54221] [PATCH 4/4] gnu: neovim: Update package style SeerLite via Guix-patches via
2022-03-02 18:40 ` Maxime Devos
2022-03-03 17:36 ` SeerLite via Guix-patches via
2022-03-02 18:33 ` [bug#54221] [PATCH 1/4] gnu: vim: Use native-search-paths to search for plugins Maxime Devos
2022-05-13 2:17 ` [bug#54221] [PATCH v2 1/2] " SeerLite via Guix-patches via
2022-05-13 2:17 ` [bug#54221] [PATCH v2 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-05-19 0:50 ` [bug#54221] [PATCH v3 1/2] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2022-05-19 0:50 ` [bug#54221] [PATCH v3 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-05-19 1:08 ` [bug#54221] [PATCH v4 1/2] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2022-05-19 1:08 ` [bug#54221] [PATCH v4 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-05-19 1:14 ` [bug#54221] [PATCH v5 1/2] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2022-05-19 1:14 ` [bug#54221] [PATCH v5 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-05-19 1:15 ` SeerLite via Guix-patches via
2022-05-24 0:41 ` [bug#54221] [PATCH v6 1/2] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2022-05-24 0:41 ` [bug#54221] [PATCH v6 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2022-05-24 1:52 ` [bug#54221] [PATCH v6 1/2] gnu: vim: Use native-search-paths to search for plugins SeerLite via Guix-patches via
2023-02-22 20:07 ` [bug#54221] [PATCH " SeerLite via Guix-patches via
2023-02-22 20:07 ` [bug#54221] [PATCH 2/2] gnu: neovim: Search and use installed plugins, like vim SeerLite via Guix-patches via
2023-08-05 12:34 ` Liliana Marie Prikler
2023-08-05 12:28 ` [bug#54221] [PATCH 1/2] gnu: vim: Use native-search-paths to search for plugins Liliana Marie Prikler
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=6002b969ed2f353fef0e8fa87d4fc7d01d3344fa.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54221@debbugs.gnu.org \
--cc=seerlite@nixnet.email \
/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).