I can easily sum most if not all of this up. According to FHS and all a distribution is not supposed to touch anything in /usr/local. /usr/local is meant for use by enduser's. The reason why the KDE tarballs and projects created by KDevelop put things in /usr/local/xxx is because these are things the enduser create.
On a normal distribution that follows FHS you will find that the moduledir will be /usr/lib/kde2. This path does not need to go into ld.so.conf because they are modules and KDE apps are the only apps that need them. Since they are the only apps that need them and they already know where to find them there is no need to tell anyone else where they live. Ivan On Thu, Aug 02, 2001 at 05:24:59PM +0200, Michael Schuerig wrote: > > I'm somewhat confused by all the places where shared libs (can) go. The > KDE debs put some (all? or only "modules"?) shared libs in > /usr/lib/kde2. KDE tarballs and projects created with KDevelop to put > them in /usr/local/lib/kde2. > > My /etc/ld.so.conf contains neither /usr/lib/kde2 nor > /usr/local/lib/kde2, but the libs in the former directory are found > nevertheless. Libs in the later directory aren't found, even after I > added it to /etc/ld.so.conf (and ran ldconfig). > > I'm somewhat confused, I must admit. Apparently, my understanding of > dynamic linking, among other things, is lacking. :-( > > Michael > > -- > Michael Schuerig GPG Fingerprint > mailto:[EMAIL PROTECTED] DA28 7DEB 5856 3365 BED9 > http://www.schuerig.de/michael/ 8365 0A30 545A 82D2 05D7 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ---end quoted text--- -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
