QSA includes its own development environment, which is hard disabled in the ebuild through the option "-no-ide". Perharps it should be always enabled or, even better, enabled or disabled with an use flag. Anyway, the current behaviour is not acceptable because some users (like myself) really need the IDE to be enabled. Reproducible: Always Steps to Reproduce: 1. emerge qsa 2. 3. Actual Results: QSA IDE is disabled. Expected Results: QSA IDE should be enabled.
If I'm not mistaken this bug has been solved in the 1.1.1 version. If so, please close this one. Thanx.
AFAICS qsa 1.1.1 doesn't build/install an ide either. It installs no binaries at all... Someone who understands the qt build system better should comment on where it goes to.
Hmm... Two years old, not fixed yet? Is anyone looking at this bug? $ equery f qsa [ Searching for packages matching qsa... ] * Contents of dev-libs/qsa-1.1.1: /usr /usr/qt /usr/qt/3 /usr/qt/3/include /usr/qt/3/include/qsaglobal.h /usr/qt/3/include/qsargument.h /usr/qt/3/include/qsconfig.h /usr/qt/3/include/qseditor.h /usr/qt/3/include/qsinputdialogfactory.h /usr/qt/3/include/qsinterpreter.h /usr/qt/3/include/qsobjectfactory.h /usr/qt/3/include/qsproject.h /usr/qt/3/include/qsscript.h /usr/qt/3/include/qsutilfactory.h /usr/qt/3/include/qsworkbench.h /usr/qt/3/include/qswrapperfactory.h /usr/qt/3/lib /usr/qt/3/lib/libqsa.prl /usr/qt/3/lib/libqsa.so -> libqsa.so.1 /usr/qt/3/lib/libqsa.so.1 -> libqsa.so.1.1 /usr/qt/3/lib/libqsa.so.1.1 -> libqsa.so.1.1.1 /usr/qt/3/lib/libqsa.so.1.1.1 /usr/qt/3/mkspecs /usr/qt/3/mkspecs/linux-g++ /usr/qt/3/mkspecs/linux-g++/qsa.prf /usr/qt/3/plugins /usr/qt/3/plugins/designer /usr/qt/3/plugins/designer/libqseditorplugin.so /usr/share /usr/share/doc /usr/share/doc/qsa-1.1.1 /usr/share/doc/qsa-1.1.1/README.gz /usr/share/doc/qsa-1.1.1/changes-1.1.1.gz
(In reply to comment #3) > Hmm... Two years old, not fixed yet? Is anyone looking at this bug? Please take into account that we have more than 500 Qt/KDE related packages to care for, but are only a handfull of more or less active maintainers.
No problem. Take your time. I don't have patches but I can test if you need testers.
Is anyone actually maintaining this? If not, you might want to remove it. Also, the ebuild is outdated, current version is 1.1.4
Zzzzz....
Could we just change "ide" use flag to "no-ide"? I think I remember, that all use _should_ enable things and not disable them. Altough - in this example - default behaviour, expected for user, would be to install ide by default. IMHO ;) just my 2 cents ;) Cheers, Przemek
This is fixed in 1.1.5 (USE=ide), closing. And no, no-* flags totally suck.