On Tue, 2019-08-27 at 16:43 +0200, Fabian Vogt wrote:
We need to make a better distinction between run-time and build- time dependencies, so that during build we pull only those dependencies that are really required for building. We mostly create "Requires:" dependencies from the end-user point of view (e.g. user needs audio support when surfing the web, as simotek argued). For the build system, that may lead to exaggerated dependencies. So we'd need something like "Requires(runtimeonly): ...".
All %{name}-devel packages usually require %{name}, so runtime deps are pulled in as dependencies of buildtime deps.
Yes, and this quasi-automatism is perhaps part of the problem? Is it really always necessary that %{name}-devel depends on %{name}?
In the hplip case you might get away with just not BuildRequiring python3-qt5.
No, that doesn't work. "configure" fails already in the compiler test. Thanks, Martin N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�