From: Jeremy Sowden <jeremy@azazel.net>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>,
Mark Mentovai <mark@mentovai.com>,
Duncan Roe <duncan_roe@optusnet.com.au>
Subject: Re: [PATCH libmnl 5/6] doc: move man-page sym-link shell-script into a separate file
Date: Wed, 3 Aug 2022 22:02:16 +0100 [thread overview]
Message-ID: <YuriWD5FTtrOsGix@azazel.net> (raw)
In-Reply-To: <2spnnr6s-1q7s-12s1-n688-463n9q162np0@vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On 2022-08-03, at 22:56:32 +0200, Jan Engelhardt wrote:
> On Wednesday 2022-08-03 22:12, Jeremy Sowden wrote:
> > We use `$(SHELL)` to run the script and exec bash if `$(SHELL)` is
> > something else. We don't hard-code the path to bash.
>
> Does it matter in practice? I don't recall seeing libmnl targeting
> a BSD platform where bash prominently isn't /bin/bash.
Apparently, there are cross-building use-cases.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-03 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 20:12 [PATCH libmnl 0/6] Doxygen Build Improvements Jeremy Sowden
2022-08-03 20:12 ` [PATCH libmnl 1/6] build: add `make dist` tar-balls to .gitignore Jeremy Sowden
2022-08-03 20:12 ` [PATCH libmnl 2/6] doc: add .gitignore for Doxygen artefacts Jeremy Sowden
2022-08-03 20:12 ` [PATCH libmnl 3/6] doc: change `INPUT` doxygen setting to `@top_srcdir@` Jeremy Sowden
2022-08-03 20:12 ` [PATCH libmnl 4/6] doc: move doxygen config file into doxygen directory Jeremy Sowden
2022-08-03 20:12 ` [PATCH libmnl 5/6] doc: move man-page sym-link shell-script into a separate file Jeremy Sowden
2022-08-03 20:56 ` Jan Engelhardt
2022-08-03 21:02 ` Jeremy Sowden [this message]
2022-08-03 20:12 ` [PATCH libmnl 6/6] doc: fix doxygen `clean-local` rule Jeremy Sowden
2022-08-04 3:45 ` [PATCH libmnl 0/6] Doxygen Build Improvements Duncan Roe
2022-08-04 10:12 ` Jeremy Sowden
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=YuriWD5FTtrOsGix@azazel.net \
--to=jeremy@azazel.net \
--cc=duncan_roe@optusnet.com.au \
--cc=jengelh@inai.de \
--cc=mark@mentovai.com \
--cc=netfilter-devel@vger.kernel.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.
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.