On Thu, Feb 26, 2009 at 10:54 AM, Michael Moss <[email protected]> wrote: > On Thu, Feb 26, 2009 at 10:40 AM, Dean McNamee <[email protected]> wrote: >> >> We don't need to stick the .so's in /usr/lib32 then do we? We can >> stick them in our own directory if that's the concern. I don't >> understand have this relates to building our own .so's or reusing >> someone elses, since either way you have the problem of us shipping >> one, and someone might already have one. > > I think we're in agreement here, but I was more just arguing against > the separate package dependency. If it's installing to our directory, > it might as well not be a separate package. >
Spoke to soon. One instance where a separate package in our directory would make sense is if ia32-libs eventually adds the needed libs. The chromium-browser package would depend on either our lib32nss3 OR ia32-libs >= whatever the known good version is. This would avoid installing our lib32nss3 on systems we know don't need it, while not conflicting with ia32-libs that provide some of the necessary libs. Michael --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
