| 1 |
On Monday 22 October 2001 22:11, you wrote: |
| 2 |
> So what was the scheme you used for /opt/kde$V (to choose the correct |
| 3 |
> one?) |
| 4 |
There was never one fully implemented. You stopped me halfway through with |
| 5 |
the /usr stuff. But it would have been the same as the current QT scheme, |
| 6 |
with the exception that we can now use eclasses to make everything much much |
| 7 |
easier. |
| 8 |
|
| 9 |
For libraries, it's enough to add kde*/lib to LDPATH (in descending order, |
| 10 |
latest versions first) and the apps will find the right library to lload. |
| 11 |
For binaries, we add $KDEDIR/bin (of the current KDE) to PATH only on KDe |
| 12 |
startup, i.e. in the /usr/X11R6/bin/wm/kde$V script, and the /bin's of all |
| 13 |
other KDEs after it in descending order. |
| 14 |
For headers, we can use eclasses to select the right dir. An ebuild will |
| 15 |
simply specify: |
| 16 |
inherit qt$V, kde$V |
| 17 |
or similar. |
| 18 |
|
| 19 |
> If the libs don't collide (ie, they are named different) and only the |
| 20 |
> headers do then all the kde-libs can be in /usr/lib and the headers has |
| 21 |
> to be in /usr/include/kde-$V or something. Then you must have a way of |
| 22 |
> choosing the correct include-path but I guess you have to anyway? |
| 23 |
The include path is the easiest part of the problem because it's only needed |
| 24 |
during compile time not run time and we have eclasses for that. |
| 25 |
|
| 26 |
-- |
| 27 |
|
| 28 |
Dan Armak |
| 29 |
Gentoo Linux Developer, Desktop Team |
| 30 |
Matan, Israel |
Archives