1 |
Hi all, |
2 |
|
3 |
Due to requests by developers of qt3 apps, I have committed a (masked) |
4 |
x11-libs/qt-x11-3.0.0 ebuild and accompanying files. |
5 |
|
6 |
It's masked because portage doesn't (yet) have the right dependency |
7 |
specification functionality. If I say DEPEND=">=x11-libs/qt-x11-2.2", |
8 |
qt-x11-3.0.0 will be used if available. Someday someone will add this |
9 |
functionality, the deadline being the release of KDE3 around Feb. 2002. |
10 |
(Please do it earlier though!) |
11 |
|
12 |
So if you just emerge this masked ebuild, portage will think it |
13 |
fullfills dependencies of qt-2.x and set QTDIR so that kde2/qt2 apps won't |
14 |
compile (or emerge). |
15 |
|
16 |
Temporary fix: rename or move the directory /usr/lib/qt-x11-3.0.0 to some |
17 |
other location, e.g. /usr/lib/qt3. Then, kde2/qt2 apps will emerge correctly. |
18 |
|
19 |
To build things against your qt3 which is now in a non-standard location, |
20 |
copy the file /etc/env.d/45qt-x11-3.0.0 to e.g. /etc/env.d/45qt3 and update |
21 |
all paths in the new copy of the file. Then run env-update and relogin. That |
22 |
takes care of runtime dynamic linking. To compile against this qt (outside of |
23 |
portage), export QTDIR as appropriate or pass --with-qt-dir to your configure |
24 |
or whatever. |
25 |
|
26 |
-- |
27 |
|
28 |
Dan Armak |
29 |
Gentoo Linux Developer, Desktop Team |
30 |
Matan, Israel |