It is absolutely the same situation as with evolution-data-server and bug #102487 - the full discription could be found there. I will attach ebuild and patch, which could resolve this issue and will use only mozilla/firefox as dependancy. This bug will also depend on bug #100597, if the firefox-use-flag is used.
Created attachment 65926 [details, diff] evolution-rpath.patch This will apply a rpath-tag to all libraries in evolution, which need it, to ensure they will correctly link at run-time to the selected nss/nprs libraries (mozilla's or firefox's)
Created attachment 65927 [details] evolution-2.2.3-r3.ebuild The ebuild, which applies the patch and which reduces the choices for nss/nspr-libraries only to mozilla and firefox.
Created attachment 65974 [details] evolution-2.2.3-r3.ebuild It could be made without the patch, but the ebuild needs the mozilla, mozilla-firefox ebuilds from bug #100597, because the pkgconfig files are not correct in the current ebuilds.
It only depends and does not block on #100597, because the ebuilds should be now in portage and it is possible to build against mozilla or mozilla-firefox (the libraries are essentially the same (even have the same size), so I don't think it is a risk building it against firefox.
Created attachment 66930 [details] evolution-2.3.8.ebuild The new evolution ebuild, which uses mozilla or mozilla-firefox.
I have forgotten about this - with nss/nspr corrected in portage and the ebuilds using only them this is not a problem anymore. so closing. the only thing probably left is make evolution and e-d-s use the pkg-config files from nss/nspr.
