From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: <devel@edk2.groups.io>, <pedro.falcato@gmail.com>,
<tlaronde@polynum.com>
Subject: Re: [edk2-devel] edksetup.sh: fix for non POSIX whereis(1)
Date: Tue, 22 Nov 2022 08:40:30 -0700 [thread overview]
Message-ID: <0bb285e2-ca66-f78a-7da9-ffd13473b61a@quicinc.com> (raw)
In-Reply-To: <CAKbZUD3rw0YNw7pq6a4rtSzjx9HOs0p2MnZ9tWypezaLvOnbKQ@mail.gmail.com>
On 11/21/22 15:22, Pedro Falcato wrote:
> I kind of dislike your solution. Does NetBSD ship /bin/which by default?
> I think replacing whereis with "which -a" would be a lot better.
> I don't think there's a 100% standard way to do this in POSIX, as which
> isn't POSIX either, and your solution seems... hacky?
"command" seems to be the POSIX way to do this?
https://pubs.opengroup.org/onlinepubs/9699919799/
Though "whereis python3" shows the following on my system:
python3: /usr/bin/python3.9-config /usr/bin/python3.9 /usr/bin/python3
/usr/lib/python3.9 /usr/lib/python3 /etc/python3.9 /etc/python3
/usr/local/lib/python3.9 /usr/include/python3.9 /usr/share/python3
/usr/share/man/man1/python3.1.gz
"which -a python3" returns:
/usr/bin/python3
/bin/python3
And "command -p -v" returns:
/bin/python3
I don't know if we need all the results from "whereis"?
--
Rebecca Cran
next prev parent reply other threads:[~2022-11-22 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 13:09 edksetup.sh: fix for non POSIX whereis(1) tlaronde
2022-11-21 22:22 ` [edk2-devel] " Pedro Falcato
2022-11-22 8:14 ` tlaronde
2022-11-22 15:40 ` Rebecca Cran [this message]
2022-11-22 16:22 ` Pedro Falcato
2022-11-22 16:26 ` tlaronde
2022-11-22 16:31 ` Pedro Falcato
2022-11-22 17:07 ` tlaronde
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-list 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=0bb285e2-ca66-f78a-7da9-ffd13473b61a@quicinc.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox