dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Robin Jarry <rjarry@redhat.com>
Subject: Re: [PATCH v2 1/2] usertools/devbind: update coding style
Date: Tue, 3 Dec 2024 09:07:52 -0800	[thread overview]
Message-ID: <20241203090752.39f9c89d@hermes.local> (raw)
In-Reply-To: <236299d7081f4a06a6f6d06eb575539582c0344f.1733224995.git.anatoly.burakov@intel.com>

On Tue,  3 Dec 2024 11:25:00 +0000
Anatoly Burakov <anatoly.burakov@intel.com> wrote:

> +
> +def check_installed(program: str, package: str) -> None:
> +    """Check if a program is installed."""
> +    if subprocess.call(
> +        ["which", program], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL
> +    ):
> +        raise DevbindError(f"'{program}' not found - please install '{package}'.")
> +

Apparently the posix way to do this is to use command -v not "which"


       command [-pVv] command [arg ...]
              Run  command  with  args  suppressing  the  normal shell function
              lookup.  Only builtin commands or commands found in the PATH  are
              executed.   If  the -p option is given, the search for command is
              performed using a default value for PATH that  is  guaranteed  to
              find  all  of the standard utilities.  If either the -V or -v op‐
              tion is supplied, a description of command is  printed.   The  -v
              option  causes  a  single word indicating the command or filename
              used to invoke command to be displayed; the -V option produces  a
              more  verbose  description.   If the -V or -v option is supplied,
              the exit status is 0 if command was found, and 1 if not.  If nei‐
              ther option is supplied and an error occurred or  command  cannot
              be  found, the exit status is 127.  Otherwise, the exit status of
              the command builtin is the exit status of command.

  reply	other threads:[~2024-12-03 17:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 15:09 [PATCH v1 0/1] Rewrite devbind Anatoly Burakov
2024-12-02 15:09 ` [PATCH v1 1/1] usertools/devbind: update coding style Anatoly Burakov
2024-12-02 17:01   ` Stephen Hemminger
2024-12-03  8:55     ` Burakov, Anatoly
2024-12-02 16:14 ` [PATCH v1 0/1] Rewrite devbind Bruce Richardson
2024-12-03  8:51   ` Burakov, Anatoly
2024-12-02 16:54 ` Stephen Hemminger
2024-12-03 11:24 ` [PATCH v2 0/2] " Anatoly Burakov
2024-12-03 11:25   ` [PATCH v2 1/2] usertools/devbind: update coding style Anatoly Burakov
2024-12-03 17:07     ` Stephen Hemminger [this message]
2024-12-04  8:59       ` Burakov, Anatoly
2024-12-03 22:16     ` Stephen Hemminger
2024-12-04  9:02       ` Burakov, Anatoly
2024-12-03 11:25   ` [PATCH v2 2/2] usertools/devbind: replace devbind Anatoly Burakov
2024-12-04  9:45 ` [PATCH v3 0/1] Rewrite devbind Anatoly Burakov
2024-12-04  9:45   ` [PATCH v3 1/1] usertools/devbind: replace devbind Anatoly Burakov
2024-12-04  9:48   ` [PATCH v3 0/1] Rewrite devbind Burakov, Anatoly
2024-12-04  9:47 ` [PATCH v3 0/2] " Anatoly Burakov
2024-12-04  9:47   ` [PATCH v3 1/2] usertools/devbind: update coding style Anatoly Burakov
2024-12-04  9:47   ` [PATCH v3 2/2] usertools/devbind: replace devbind Anatoly Burakov
2025-02-18  9:29   ` [PATCH v3 0/2] Rewrite devbind Burakov, Anatoly

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=20241203090752.39f9c89d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=rjarry@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).