Bugzilla Bug 7097

I have installed Qt in a non-standard location. When I tried to emerge qcad,
the
compilation aborted.
After I had removed the line "export QTDIR=/usr/qt/3" in the ebuild file, the
program did compile.

danarmak: if you remove the export QTDIR=... in the ebuilds it should work 
(works here).  

Yes, well, the export lines are there because there's only one QTDIR variable 
but many qt versions. I can remove the QTDIr=/usr/qt/3 lines from ebuilds 
today, but not the QTDIR=/usr/qt/2 lines from ebuilds using QT2. And when QT-4 
is released in a year or two, what will we do? qt-3 ebuild will then need this 
setting again. 
 
There is, of course, the set-qtdir() (and need-qt()) function in 
kde-functions.eclass. This is exactly the reason it exists. Should we make all 
qt ebuilds use them? I'l think about that because I have some objections... 
 
Meanwhile do you have any objections to making a symlink form /usr/qt/3 to 
whereever your custom qt is? That way all ebuilds will work no matter what 
while I decide what we should do. 

I'm no longer sure what my objections were, so I'm making the ebuild use
set-qtdir() 
from kde-functions.eclass. I've also added an ebuild for 1.5.4. 

A quick grep on QTDIR shows that there are still some ebuilds not using this
function. Is there a reason for that?