Ken Moffat wrote: > > Firefox3 had *some* discussion, but there is still a lack of any > obvious consensus. I think I'm with dj on this one, but I need to > find time to see if I can make the included nss in 3.0.4/1.9.0.4 use > the system libraries such as zlib. I may look at the system zlib a little later too, but just to reiterate on this and save a search, my suggestion was that we should provide both separate nspr and nss for the system. However, we should add a warning to use the included nss on Mozilla supplied packages. I'm not sure if this warning should be carried to other packages or not...maybe the nss page is the proper place?
For the editors and contributors: Any package that can use a system installed nss library, needs verification that libcrfm is not included (and I honestly don't know its importance, only that it is built static only and is used in xulrunner/firefox3). If it is included, then that package requires a rebuild if a new version of nss is installed (and probably a warning or note in the affected package's instructions). With as little as I have been able to gather by way of grep, the rest of the static libs installed by nss or nspr should be able to be removed, but I haven't tested that theory just yet so use caution. Ken, where were you with that? As for Seamonkey and Thunderbird, they will not use the newer nss/nspr so the included ones are the only option ATM. As for using the firefox included nss as a system nss library...I am undecided as of yet, again, because I haven't tried that just yet. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
