On Thu, Feb 26, 2009 at 10:14 AM, Adam Langley <[email protected]> wrote: > On Thu, Feb 26, 2009 at 10:10 AM, Michael Moss <[email protected]> wrote: >> For those who haven't been following this whole saga, note that there >> is an Ubuntu bug for this, and so far they have been unwilling to >> backport it to Hardy. They applied a fix (unfortunately broken) to >> Intrepid, but don't seem inclined to muck with Hardy unless it's a >> security fix. At this point, any new requests would be targeted to >> Jaunty by default. > > As I understand it, NSS must be built as a .so, at least in part. > Since we cannot statically link NSS, I don't believe it should be in > our tree. Since we're already going to provide packages for 32-bit > systems, we can also provide a libnss-32 (or whatever) package and > make chromium-browser depend on that.
The main problem with that is that it might conflict with distros that already have some or all of the 32-bit stuff (e.g. Intrepid). If we depend on lib32nss2, to get /usr/lib32/libnss3.so, but the distro supplies that in ia32-libs (as it normally would), then our dependency will conflict with ia32-libs and chromium-browser won't install. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
