On Thu, Feb 26, 2009 at 10:29 AM, Adam Langley <[email protected]> wrote: >> 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. > > We'll have different repos for each different supported release and > distribution anyway, so I don't believe this is a problem.
Currently, Google has a single public repo for all .rpm distros, and another single public repo for all .deb distros. Our packages are all portable across all popular distros. It would be sad to have to break that. Breaking it into multiple required packages may also add complexity to the install process; I suspect we would have higher user install success rate if we keep all the required bits in a single package. - Dan --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
