<qa team lead hat> In short - apropriate REQUIRED_USE with setting recommended USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5")
</qa team lead hat> That's most painless decision for both developers and users. Developers do not need to maintain ugly dependencies like DEPEND="qt4 ? ( qt5 ( dev-qt/qtcore:5 ) !qt5 ( dev-qt/qtcore:4 ) ) ... " and other mess. </qa team lead hat> Users will have default behaviour for empty make.conf. If they adjust they make.conf to globally include/exclude some Qt-related USEs - they are already moving from default and that's why - they can add apropriate options to package.use 02.08.2015 19:34, Ben de Groot пишет: > Recently some team members of the Qt project have adopted these ebuild > policies: https://wiki.gentoo.org/wiki/Project:Qt/Policies > > I have an issue with the policy adopted under "Requires one of two Qt > versions". In my opinion, in the case where a package offers a choice > between qt4 or qt5, we should express this in explicit useflags and a > REQUIRED_USE="^^ ( qt4 qt5 )". This offers the user the clearest choice. > > Other developers state that users are not interested in such > implementation details, or that forced choice through REQUIRED_USE is > too much of a hassle. This results in current ebuilds such as quassel to > not make it clear that qt4 is an option. > > This goes against the principle of least surprise, as well as against QA > recommendations. I would like to hear specifically from QA about how we > should proceed, but comments from the wider developer community are also > welcome. > > -- > Cheers, > > Ben | yngwin > Gentoo developer > -- Best regards, Sergey Popov Gentoo developer Gentoo Desktop-effects project lead Gentoo Quality Assurance project lead Gentoo Proxy maintainers project lead
signature.asc
Description: OpenPGP digital signature
