All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,  jsnow@redhat.com,
	 peter.maydell@linaro.org, thuth@redhat.com,
	 alex.bennee@linaro.org,  berrange@redhat.com
Subject: Re: [PATCH 03/10] meson: prefer 'sphinx-build' to 'sphinx-build-3'
Date: Wed, 22 Feb 2023 17:26:00 +0100	[thread overview]
Message-ID: <87cz61ll9j.fsf@pond.sub.org> (raw)
In-Reply-To: <20230222143752.466090-4-pbonzini@redhat.com> (Paolo Bonzini's message of "Wed, 22 Feb 2023 15:37:45 +0100")

Paolo Bonzini <pbonzini@redhat.com> writes:

> From: John Snow <jsnow@redhat.com>
>
> Once upon a time, "sphinx-build" on certain RPM platforms invoked
> specifically a Python 2.x version, while "sphinx-build-3" was a distro
> shim for the Python 3.x version.
>
> These days, none of our supported platforms utilize a 2.x version, so it
> should be safe to search for 'sphinx-build' prior to 'sphinx-build-3',
> which will prefer pip/venv installed versions of sphinx if they're
> available.
>
> This adds an extremely convenient ability to test document building
> ability in QEMU across multiple versions of Sphinx for the purposes of
> compatibility testing.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> Message-Id: <20230221012456.2607692-6-jsnow@redhat.com>

Accident?

> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  docs/meson.build | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/meson.build b/docs/meson.build
> index 9136fed3b730..906034f9a87f 100644
> --- a/docs/meson.build
> +++ b/docs/meson.build
> @@ -1,5 +1,5 @@
>  if get_option('sphinx_build') == ''
> -  sphinx_build = find_program(['sphinx-build-3', 'sphinx-build'],
> +  sphinx_build = find_program(['sphinx-build', 'sphinx-build-3'],
>                                required: get_option('docs'))
>  else
>    sphinx_build = find_program(get_option('sphinx_build'),

In review of the original "[PATCH v3 5/6] meson: prefer 'sphinx-build'
to 'sphinx-build-3'", I challenged the check for sphinx-build-3.



  reply	other threads:[~2023-02-22 16:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 14:37 [PATCH v4 0/9] improvement to Python detection, preparation for dropping 3.6 Paolo Bonzini
2023-02-22 14:37 ` [PATCH 01/10] python: support pylint 2.16 Paolo Bonzini
2023-02-22 14:37 ` [PATCH 02/10] python: drop pipenv Paolo Bonzini
2023-03-15 21:16   ` Philippe Mathieu-Daudé
2023-03-15 23:02     ` John Snow
2023-03-16  8:54       ` Philippe Mathieu-Daudé
2023-03-16 10:49         ` Jan Richter
2023-03-16 14:26         ` John Snow
2023-02-22 14:37 ` [PATCH 03/10] meson: prefer 'sphinx-build' to 'sphinx-build-3' Paolo Bonzini
2023-02-22 16:26   ` Markus Armbruster [this message]
2023-02-22 16:53     ` Paolo Bonzini
2023-02-22 14:37 ` [PATCH 04/10] configure: protect against escaping venv when running Meson Paolo Bonzini
2023-02-22 15:04   ` Daniel P. Berrangé
2023-02-22 15:25     ` Paolo Bonzini
2023-02-22 14:37 ` [PATCH 05/10] configure: Look for auxiliary Python installations Paolo Bonzini
2023-02-22 15:19   ` Daniel P. Berrangé
2023-02-22 14:37 ` [PATCH 06/10] lcitool: update submodule Paolo Bonzini
2023-02-22 15:07   ` Daniel P. Berrangé
2023-02-22 14:37 ` [PATCH 07/10] docs/devel: update and clarify lcitool instructions Paolo Bonzini
2023-02-22 15:11   ` Daniel P. Berrangé
2023-02-22 14:37 ` [PATCH 08/10] ci, docker: update CentOS and OpenSUSE Python to non-EOL versions Paolo Bonzini
2023-02-22 15:14   ` Daniel P. Berrangé
2023-02-22 14:37 ` [PATCH 09/10] Python: Drop support for Python 3.6 Paolo Bonzini
2023-02-22 15:16   ` Daniel P. Berrangé
2023-02-22 15:28     ` Paolo Bonzini
2023-02-22 16:31   ` Markus Armbruster
2023-02-22 17:02     ` Paolo Bonzini
2023-03-13 17:05   ` Daniel P. Berrangé
2023-03-15 12:53     ` Thomas Huth
2023-02-22 14:37 ` [PATCH 10/10] configure: Add courtesy hint to Python version failure message Paolo Bonzini
2023-03-21 14:11 ` [PATCH v4 0/9] improvement to Python detection, preparation for dropping 3.6 Philippe Mathieu-Daudé

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=87cz61ll9j.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 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.