Currently I have disabled the "exceptions" flag in all Qt components, using the standard USE flag method, e.g.: cat /etc/portage/package.use/x11-libs x11-libs/qt-gui -exceptions However, qt-xmlpatterns seems to be the only Qt ebuild with "exceptions" hard coded: DEPEND="~x11-libs/qt-core-${PV}[aqua=,debug=,exceptions]" Which pulls in the exceptions flag for every other Qt package. I've circumvented this by just removing ",exceptions" from the above ebuild, but ideally it should be added to IUSE instead, for those who do actually need it. Please consider allowing this option, since despite Nokia's "recommendation", exceptions are useless to everyone except Qt developers, and it only serves to increase build time and bloat. It should also be noted that, despite various warnings from others, qt-xmlpatterns does in fact build and run successfully without the exceptions flag. Reproducible: Always Steps to Reproduce: 1. emerge x11-libs/qt-xmlpatterns Actual Results: "exceptions" flag forced on all Qt components. Expected Results: I don't want "exceptions". Ever. Thanks.
Also see bug 240185.
(In reply to comment #1) > Also see bug 240185. As you can see from that bug, this option was disabled in qt-xmlpatterns, because at the time it resulted in compile failure. If that has since been fixed, then we should revisit this decision.
No, the situation is unchanged since then, and won't change for qt5 either. In fact, there's nothing to fix here since upstream doesn't consider the usage of exceptions a "bug" (and qt-xmlpatterns does require them).
(In reply to comment #3) > No, the situation is unchanged since then, and won't change for qt5 either. > In fact, there's nothing to fix here since upstream doesn't consider the > usage of exceptions a "bug" (and qt-xmlpatterns does require them). It would be nice if we could add a brief comment ontop of IUSE on every ebuild that requires +exceptions to avoid duplicates in the future.
(In reply to comment #4) > (In reply to comment #3) > > No, the situation is unchanged since then, and won't change for qt5 either. > > In fact, there's nothing to fix here since upstream doesn't consider the > > usage of exceptions a "bug" (and qt-xmlpatterns does require them). > > It would be nice if we could add a brief comment ontop of IUSE on every > ebuild that requires +exceptions to avoid duplicates in the future. Only qt-xmlpatterns has a hard dependency on them being enabled IIRC.
Re-reading this sentence: "It should also be noted that, despite various warnings from others, qt-xmlpatterns does in fact build and run successfully without the exceptions flag." from the OP, I think what he actually wanted to say is that qt-xmlpatterns doesn't require exceptions enabled in *qt-core*, i.e. we can drop the USE dependency. But qt-xmlpatterns still has to be built with exceptions, so there's no point in adding USE=exceptions to qt-xmlpatterns.
Re: comment 6 Yes, that's what I meant: qt-xmlpatterns builds and runs successfully without its dependancy, qt-core, being built with exceptions, so please can this be provided as a USE flag option (in the qt-core ebuild itself), rather than pushed onto qt-core by qt-xmlpatterns without option.
No, it doesn't need a USE flag, we will just drop the [exceptions] USE flag dep from qt-xmlpatterns :-)
Even better. :)
(In reply to comment #8) > No, it doesn't need a USE flag, we will just drop the [exceptions] USE flag > dep from qt-xmlpatterns :-) Done, thanks for reporting.
