It can run though the emerge, but since "QTBASE=/usr/qt/3" is set in the ebuild, all configure files just point to that place. Reproducible: Always Steps to Reproduce: 1. ecopy =x11-libs/qt-3.3.8-r4 2.emerge =x11-libs/qt-3.3.8-r4 3.build any source that requare Qt3 ( eg. kde-base/kdelibs-3.5.10-r2 ). Actual Results: You may failed in ./configure or later.
ok, so what is the fix? just change QTBASE, or..?
I read the ebuild of qt-4, which is in the portage tree, and find no path in. So maybe it should be done this way. But I am still a bit confused on {ED} and {EROOT}, so I didn't run some test yet.
I just make a test and find "QTBASE={EROOT}/usr/qt/3" will make the files to install to /home/galaxy/gentoo/\{EROOT\}/usr/qt/3 . And during the compiling, it just use freetype2 headeds from the real root of the system. So , how should I change QTBASE ?
Not sure offhand. ecopy is simply a best effort script, it is of not much use to us to know that a package cannot be ecopy'd correctly. It would be: ${EROOT} not {EROOT} QTBASE=${EROOT}/usr/qt/3 Have you read http://www.gentoo.org/proj/en/gentoo-alt/prefix/techdocs.xml which explains things quite well IMO.
I read that webpage. And find some knowledge on ebuild itself is required to do the transform. Just like {EROOT} lead to '/home/galaxy/gentoo/\{EROOT\}/usr/qt/3' , ${EROOT} leads to 'home/galaxy/gentoo///home/galaxy/gentoo/usr/qt/3' . ( I don't know why starts without '/' ) So, other function must also be edited to specify the install path.
ecopy is just a little best-effort helper, manual checking its results is always necessary.
Sorry for a long delay. Why this is "RESOLVED" ? A patch is needed to setup this package with portage.
bug was about ecopy. Change the description accordingly and provide info on what exactly where needs to be fixed.
QT-3 is a no-go, sorry
