Currently qt-creator requires qt-gui[qt3support]. But I've successfully built Qt Creator 2.0.0 and 2.0.1 on Qt 4.7 builds with disabled qt3support, and never had any problems with it.
It is a runtime dependency. You need it when you want to use the Qt3support API. If I drop qt3support then I will have to drop all the qt-* runtime deps because nothing really depends on them. Qt-creator does not need qt-dbus, qt-webkit etc to build it it requires them if you want to have a full working qt-creator since it depends to the whole Qt4 API.
Enabling qt3support in qt-gui brings bloat functions, so this dependency differs from others
+ 15 Nov 2010; Markos Chandras <hwoarang@gentoo.org> + qt-creator-2.0.1.ebuild, qt-creator-2.1.0_beta2.ebuild, metadata.xml: + Add new qt3support useflag per user request. Bug #345443 + Fair enough. I added a new useflag 'qt3support' to allow users control this behavior
IMHO qt3support (considered as an additional API) does not deserve a USE flag in this particular case. If a developer using qt-creator needs it as a dependency for its own project, he should be installing it manually. More generically, a package should only depend on other packages which are actually used (either at build-time or at run-time) and not on libraries which might be required by third party projects. So, if qt-creator itself doesn't really need qt3support, please remove the USE flag altogether.
The same applies to other Qt APIs which are not required to build or run qt-creator itself.
As I said before, if you follow this approach then you need to drop all the qt-* dependencies and pretty much have a qt-creator only capable to do C++ development with a limited Qt4 API available ( the only that qt-gui which is the only dep afaik brings )
(In reply to comment #6) > As I said before, if you follow this approach then you need to drop all the > qt-* dependencies and pretty much have a qt-creator only capable to do C++ > development with a limited Qt4 API available ( the only that qt-gui which is > the only dep afaik brings ) > And what's the problem? If a user (C++ developer actually) needs something else (e.g. additional APIs), it's because of *his* projects, not because of qt-creator itself. (BTW I guess the help viewer requires qt-webkit or qt-assistant...)
I am doing some testing around here. Seems like most of the qt-* packages are actual build dependencies. Qt-assistant is required to view the help menu etc yes. Ok then I will probably refactor the deps, moving runtime deps to build deps and drop qt3support entirely if I manage to compile it without qt3support
Nice :) Thanks a lot Markos!
15 Nov 2010; Markos Chandras <hwoarang@gentoo.org> qt-creator-2.0.1.ebuild, qt-creator-2.1.0_beta2.ebuild, metadata.xml: Refactor dependencies. Drop qt3support entirely and kde/phonon dependencies as well. Bug #345443 It should be ok now
The changes broke Creator completely for me. I am now unable to load or create projects. See bug 345757.
