diff options
author | Ionen Wolkens <ionen@gentoo.org> | 2023-08-25 15:55:43 -0400 |
---|---|---|
committer | Ionen Wolkens <ionen@gentoo.org> | 2023-09-05 09:01:08 -0400 |
commit | 1c1c5f921cb4b20a53a31b6353a4d456881bb6a0 (patch) | |
tree | 778a1fc3a07bc3409246e6f30eb87ebc8260004d /eclass/qt6-build.eclass | |
parent | dev-qt/qtbase: refactor use/dependences handling (diff) | |
download | gentoo-1c1c5f921cb4b20a53a31b6353a4d456881bb6a0.tar.gz gentoo-1c1c5f921cb4b20a53a31b6353a4d456881bb6a0.tar.bz2 gentoo-1c1c5f921cb4b20a53a31b6353a4d456881bb6a0.zip |
dev-qt/qtbase: decouple qttest from USE=gui, enable by default
Been finding this kind of confusing, and having every ebuilds that
run tests depend on [gui] does not seem right, and also prevent
doing minimalist tests to find issues.
This leaves two option:
1. IUSE="+testlib"
2. enable unconditionally
1 seems sane, but it's not that unusual that revdeps need qttest
for building (even if not running tests, see packages depending
on dev-qt/qttest:5 without 'test?'). qtdeclarative also fails
without it last I know of, meaning most people would need it.
And then qttest has a rather small footprint, rather than hunt
what needs it or not it seems simpler to just always have it
(embedded edge cases can still use MYCMAKEARGS or INSTALL_MASK).
Skipping revbump given was already done once in this commit batch.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'eclass/qt6-build.eclass')
0 files changed, 0 insertions, 0 deletions