| 1 |
mån 2001-10-22 klockan 22.18 skrev Dan Armak: |
| 2 |
> On Monday 22 October 2001 22:11, you wrote: |
| 3 |
> > So what was the scheme you used for /opt/kde$V (to choose the correct |
| 4 |
> > one?) |
| 5 |
> There was never one fully implemented. You stopped me halfway through with |
| 6 |
> the /usr stuff. But it would have been the same as the current QT scheme, |
| 7 |
> with the exception that we can now use eclasses to make everything much much |
| 8 |
> easier. |
| 9 |
> |
| 10 |
> For libraries, it's enough to add kde*/lib to LDPATH (in descending order, |
| 11 |
> latest versions first) and the apps will find the right library to lload. |
| 12 |
|
| 13 |
Hmm .. if this is possible, putting all libs in /usr/lib should be too. |
| 14 |
|
| 15 |
> For binaries, we add $KDEDIR/bin (of the current KDE) to PATH only on KDe |
| 16 |
> startup, i.e. in the /usr/X11R6/bin/wm/kde$V script, and the /bin's of all |
| 17 |
> other KDEs after it in descending order. |
| 18 |
|
| 19 |
It shouldn't be in /usr/X11R6/bin/wm/kde$V (only XFree86 should install |
| 20 |
things in /usr/X11R6). |
| 21 |
|
| 22 |
Hmm, this means that no KDE-apps will have there binaries in /usr/bin, |
| 23 |
or? |
| 24 |
|
| 25 |
> For headers, we can use eclasses to select the right dir. An ebuild will |
| 26 |
> simply specify: |
| 27 |
> inherit qt$V, kde$V |
| 28 |
> or similar. |
| 29 |
|
| 30 |
Hmm.. this will cause lots of troubles for developers (KDE/QT-developers |
| 31 |
that is) that has to make special cases for compiling things on Gentoo. |
| 32 |
|
| 33 |
> > If the libs don't collide (ie, they are named different) and only the |
| 34 |
> > headers do then all the kde-libs can be in /usr/lib and the headers has |
| 35 |
> > to be in /usr/include/kde-$V or something. Then you must have a way of |
| 36 |
> > choosing the correct include-path but I guess you have to anyway? |
| 37 |
> The include path is the easiest part of the problem because it's only needed |
| 38 |
> during compile time not run time and we have eclasses for that. |
| 39 |
|
| 40 |
As said above this is good for packages in portage but sucks pretty |
| 41 |
badly when you want to compile something manually. |
| 42 |
|
| 43 |
Perhaps we can solve this by making symlink from /usr/include/kde -> |
| 44 |
/usr/include/kde-$V (not sure of how kde installs its headers). |
| 45 |
This does however mean that all kde-$V ebuilds has to make this symlink |
| 46 |
and the one that is emerged last will be the one that is used (and if |
| 47 |
you unmerge it no link will be there which isn't a good scheme). |
| 48 |
|
| 49 |
But as said, if it is possible to add them all to LDPATH (and it finds |
| 50 |
the correct lib to link) it should be possible to install them all in |
| 51 |
/usr/lib (ie. they have different version-numbers)? |
| 52 |
|
| 53 |
How do other distros solve this? |
| 54 |
|
| 55 |
Regards, |
| 56 |
Mikael Hallendal |
| 57 |
|
| 58 |
-- |
| 59 |
|
| 60 |
Mikael Hallendal |
| 61 |
Gentoo Linux Developer, Desktop Team Leader |
| 62 |
CodeFactory AB, Stockholm, Sweden |
Archives