In <news:[email protected]>, Wladimir Palant <[email protected]> wrote:
> On Dec 18, 11:00 am, Wladimir Palant <[email protected]> wrote: > > From the look of it, Gentoo simply gets the source code from the FTP > > server - version 3.12.3 there comes with ckbi 1.73, only version > > 3.12.3.1 has ckbi 1.75. > > Looking further into this, I see why I've seen only two reports on > this issue so far. Official builds for both Firefox and SeaMonkey come > with their own NSS library, those always work correctly. Only vendor- > supplied builds rely on an independent NSS package which could be > outdated (but not always is, at least some distributions already use > NSS 3.12.4). Gentoo also has 3.12.4 and 3.12.5, but neither of them are marked stable yet. I went ahead and compiled 3.12.4, and everything seems to be as it should be -- but I don't know if that's only due to me selecting the checkbox earlier. You're right about Gentoo getting the NSS source from the FTP server (it's then of course mirrored on Gentoo servers). Since Gentoo is source-based distro, the preference is for system libraries, so the same library doesn't have to be compiled over and over for each app. (NSS is a quick compile, but some others aren't.) Do any of you know if Mozilla supplies source patches to NSS tarballs when the certificate store is updated, or does it just wait for the next NSS version number? If there are patches provided, I'll point the Gentoo maintainer to them. -- »Q« /"\ ASCII Ribbon Campaign \ / against html e-mail X <http://asciiribbon.org/> / \ _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
