From d017d572ee7d66b19890c5a23aa42147a886657b Mon Sep 17 00:00:00 2001 From: Miro Hrončok Date: Jun 15 2022 09:19:59 +0000 Subject: Introduce a tests bcond Note that listing tests requirements in build-system.requires is not a standard practice. Dependency loops: • python-decopatch → python-pytest-cases → python-pytest-steps → python-pytest-harvest → python-decopatch • python-decopatch → python-pytest-cases → python-pytest-harvest → python-decopatch • python-decopatch → python-pytest-cases → python-pytest-steps → python-decopatch • python-decopatch → python-pytest-cases → python-decopatch • python-decopatch → python-decopatch --- diff --git a/python-decopatch.spec b/python-decopatch.spec index 77f2ab3..6f8eae5 100644 --- a/python-decopatch.spec +++ b/python-decopatch.spec @@ -10,6 +10,11 @@ Source0: %{pypi_source decopatch} BuildArch: noarch BuildRequires: pyproject-rpm-macros +# There is a build dependency loop when built with tests. +# It involves pytest-cases, pytest-harvest, pytest-steps. +# This bcons allows to bootstrap it. +%bcond_without tests + %global _description %{expand: Because of a tiny oddity in the python language, writing decorators without help can be a pain because you have to handle the no-parenthesis usage explicitly. @@ -27,21 +32,26 @@ Summary: %{summary} %autosetup -n decopatch-%{version} cat >pyproject.toml <