mirror of
https://github.com/qemu/qemu.git
synced 2026-07-08 17:56:38 +00:00
'tooling' contains depedencies required to run various tools (like qmp-shell) as well as dependencies required to run "make check", and as such, we promise that these dependencies can be sourced from the user's distribution repository or from vendored packages so that "make check" can be executed offline in an isolated build environment. In contrast, pygdbmi is only needed for functional tests and not tests in general; we do not make the same offline/isolated guarantees for functional tests, and this dependency group is allowed to fetch dependencies from PyPI at runtime. For the time being, amend the "check-venv" target to install both dependency groups, to avoid a duplicate dependency between them. By the end of this series, however, "check-venv" will be eliminated in favor of always installing "tooling" at configure time and allowing "functests" to be installed on-demand as needed by meson/ninja. Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Message-ID: <20260218213416.674483-5-jsnow@redhat.com> Signed-off-by: John Snow <jsnow@redhat.com>
45 lines
2.0 KiB
TOML
45 lines
2.0 KiB
TOML
# This file describes Python package requirements to be
|
|
# installed in the pyvenv Python virtual environment.
|
|
#
|
|
# Packages are placed in groups, which are installed using
|
|
# the ensuregroup subcommand of python/scripts/mkvenv.py.
|
|
# Each group forms a TOML section and each entry in the
|
|
# section is a TOML key-value list describing a package.
|
|
# All fields are optional; valid fields are:
|
|
#
|
|
# - accepted: accepted versions when using a system package
|
|
# - installed: fixed version to install in the virtual environment
|
|
# if a system package is not found; if not specified,
|
|
# defaults to the same as "accepted" or, if also missing,
|
|
# to the newest version available on PyPI.
|
|
# - canary: if specified, use this program name to present more
|
|
# precise error diagnostics to the user. For example,
|
|
# 'sphinx-build' can be used as a bellwether for the
|
|
# presence of 'sphinx' in the system.
|
|
|
|
[meson]
|
|
# The install key should match the version in python/wheels/
|
|
meson = { accepted = ">=1.5.0", installed = "1.10.0", canary = "meson" }
|
|
pycotap = { accepted = ">=1.1.0", installed = "1.3.1" }
|
|
|
|
[meson-rust]
|
|
# The install key should match the version in python/wheels/
|
|
meson = { accepted = ">=1.10.0", installed = "1.10.0", canary = "meson" }
|
|
|
|
[docs]
|
|
# Please keep the installed versions in sync with docs/requirements.txt
|
|
sphinx = { accepted = ">=3.4.3", installed = "6.2.1", canary = "sphinx-build" }
|
|
sphinx_rtd_theme = { accepted = ">=0.5", installed = "1.2.2" }
|
|
|
|
# This test group is for dependencies required to run various tooling
|
|
# and tests that should always be installed at configure time. It should
|
|
# only include dependencies that can be guaranteed via configure from
|
|
# system packages, or python packages we vendor.
|
|
[tooling]
|
|
"qemu.qmp" = { accepted = ">=0.0.5", installed = "0.0.5" }
|
|
|
|
# This test group is for functional tests, and can include dependencies
|
|
# fetched from PyPI.
|
|
[functests]
|
|
pygdbmi = { accepted = ">=0.11.0.0", installed = "0.11.0.0" }
|