We usually go for a full path to the interpreter rather than env and 
relying on the user's PATH including /usr/local/bin

-- 
  Sent from a phone, apologies for poor formatting.

On 23 October 2024 12:01:12 Florian Obser <florian@openbsd.org> wrote:

> Hi there,
>
> so I'm writing IETF drafts now.
>
> Please stop laughing.
>
> We already have xml2rfc. I'll poke at kramdown-rfc2629 (ruby) next,
> because I'm not going to write raw xml...
>
> Another thing I'd like to have is idnits
> https://github.com/ietf-tools/idnits/tree/v2
>
> Which is just a bash script, and yes, it's bash.
> So it would need a rundep on shells/bash and a slap with sed:
> 's,/bin/bash,/usr/bin/env bash,'
>
> Is there an example for such a port or is that just silly?
>
> v3 is a rewrite in JavaScript for some bizarre reason, so that's going
> to be fun.
>
> Thanks,
> Florian
>
> --
> In my defence, I have been left unsupervised.