Currently, when emerge app-text/djvu without qt3 USE flag, emerge promotes: * The standalone djvu viewer, djview, will not be compiled. * Add "qt3" to your USE flags if you want it. The message is misleading because it doesn't not mention the QT4's djviewe4 at all, unfamiliar user (such as me) tends to add qt3 use flag instead of emerge the newer djviewe4. I suggest to add some text in the warning message: * The standalone djvu viewer, djview, will not be compiled. * Add "qt3" to your USE flags if you want it. * QT4 user should emerge app-text/djview4 instead. Reproducible: Always Steps to Reproduce: emerge -a app-text/djvu without qt3 use flag Expected Results: suggest user to emerge djview4
Should likely remove app-text/djvu or package move it to app-text/djview4, or at least drop USE="qt3" wrt bug 283429.
(In reply to comment #1) > Should likely remove app-text/djvu or package move it to app-text/djview4, > or at least drop USE="qt3" wrt bug 283429. > djvu (library part) is required by other djvu viewers, as for example okular. So most logical would be to leave djvu as library/tools package, while keeping viewer functions separate in djview4.
Qt3 support dropped.
My surgical removal of optional qt3 use from djvu was reverted, but x11-libs/qt:3 is still scheduled for p.mask next month and removal in March (see bug 283429). Dependency on qt:3 should be removed.
Fixed in 3.5.22-r1. Ben, next time, please, if maintainer requested in advance not to drop some functionality (nsplugin) and after you still did that (I hope that by mistake) and then were asked you to revert partially broken commit (had typos, forgot about localizations and some unused things...) PLEASE PLEASE next time REVERT COMMIT YOURSELF. This kind of actions just help to loose any enthusiasm...