Here is an ebuild for qt-embedded 3.3.4. It includes the patch from bug #78674 to fix library path compiling errors and sandbox access violations. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 50367 [details] ebuild for qt-embedded 3.3.4
Created attachment 50369 [details] ebuild for qt-embedded 3.3.4 My bad, forgot to remove the old version info from the header tag in the previous ebuild.
*** Bug 61021 has been marked as a duplicate of this bug. ***
kde herd: I took some time to update the qt-embedded ebuild and to do a long-awaited cleanup. I have two questions: 1) should we keep the custom build of qt-embedded that the ebuild does with USE="build"? I think not, it was used for an (old?) installer project, but it was ages ago and probably nobody uses it now. 2) with respect to bug 71655: I think the best solution is to not add neither QTDIR nor QMAKESPEC to the environment, to be absolutely sure that we don't conflict with standard Qt. Consider that nothing in the portage tree depends on qt-embedded, the only exceptions being media-tv/{mythtv,mythbrowser}, but in newer versions qt-embedded was also removed from there. If someone uses qt-embedded for his own project, he just have to set QTDIR and QMAKESPEC to the values he desires. This is explained in an einfo at the end of the ebuild. If it's ok, I can commit the ebuild in a few days.
I'll ask about 1) on gentoo-dev.
In gentoo-dev it seems that no one cares about qt-embedded anymore... 3.3.4 is now in portage.
