It is essentially the same bug as #102487, the problem is that gaim-encryption link at compile-time to nss/nspr libraries, but in case mozilla/mozilla-firefox are installed (which is probably the case in 90%), at run-time it will link to the mozilla/mozilla-firefox set of libraries, depending on what comes exported first in ld.so.conf. The ebuild, which I'll attach depends on bug #100597, because the installed {mozilla|firefox}-nspr is not correct in the portage-ebuilds, and the other pkg-configs do not add the -Wl,-R${libdir} to ensure consistent run-time linking. Moreover the ebuild for firefox from bug #100597 is needed for the firefox-use-flag in order for the package to compile correctly, because it installs the needed nss/nspr-includes. The ebuild removes the dependancies on nss/nspr, because as said earlier, they will not be used in most cases (but only if mozilla and firefox are not installed)
Created attachment 65936 [details] gaim-encryption-2.38-r1.ebuild The ebuild. It will build the plugin by default against mozilla, and against firefox, if the firefox-use flag is used.
Changed the name, as the ebuilds from bug #100597 are already in portage, and the consistency of the run-time linking is not a problem anymore. It simply adds the possibility to build against firefox.
You neglected to allow for the standalone nspr package, so you wouldn't need either mozilla or mozilla-firefox. I would wrap the whole firefox/!firefox check in a mozilla USE flag check as well. I'll talk things over with other devs on the firefox USE flag.
(In reply to comment #3) > You neglected to allow for the standalone nspr package, so you wouldn't need > either mozilla or mozilla-firefox. I would wrap the whole firefox/!firefox > check in a mozilla USE flag check as well. I'll talk things over with other > devs on the firefox USE flag. Yes, I know but you could not guarantee the linking if you use the nss/nspr packages, there are already bugs about this and I think the resolution is not so trivial, because nss/nspr do not provide pkg-config files, so the makefile would have to be patched, the nss/nspr should also be patched. The breakage would occur on installing mozilla or mozilla-firefox after installing this with nss/nspr, because of possible incopatible versions.
Everything in the tree is being moved to build against system nss/nspr mozilla will be removed from tree as soon as a seamonkey is marked stable, which is a bit out still.
