emerge clobbers rpm-installed libraries?

[nmr_spectrometer]

Yes this does have to do with a desktop app, so don't poo-poo the thread yet.

I've got an application that uses the 'xview' library (libxview.so.3) and the quickest and easiest way to install it was to install a binary rpm. (In the spirit of gentoo I at least tried to rpm --rebuild xview-nnn.src.rpm but I couldn't get it to work). I guess that part of the rpm install runs ldconfig to update the library paths. libxview gets installed in a funny place (/usr/openwin/lib) but after the rpm install my application can link to it just fine.

However, if I do an emerge (of anything at all), afterwards ldconfig -v shows that my libxview is no longer in the ldpath. I guess that the rpm install is updating /etc/ld.so.conf which is getting clobbered by subsequent emerges. Where is the "protected" ld.so.conf that I can edit it? The file says it's generated by env-update but I can't find anything in /etc/env.d that refers to ld.so.conf so I'm stuck.

Thanks for all your help.

[nmr_spectrometer]

*head slapping sound*

Okay, so I just edited /etc/env.d/00basic, and added /usr/openwin/lib to LDPATH. We'll see if that works.

Please pardon me for cluttering up the forum.