On Wed, May 12, 2010 at 05:43:37AM +0000, Sune Vuorela wrote: > It is the 3rd copy of webkit code in the archive, again most likely > from a different branch point. (webkit source package building the gtk > frontend to webkit, qt4-x11 building qtwebkit and now chrome)
Right, but it's no more the fault of chromium-browser than it's the
fault of the other 2 copies. All in all, we can all easily guess that
the number of our users interested in using chromium-browser (i.e. one
of our priorities) matches quite easily the number of our users
interested in using the other two front-ends. So, if we have to fix a
threshold (and I hope we don't!), one might wonder why we should keep
chrome out and not one of the others.
The point is then how each of the copies is handled individually by
upstream, security-wise (and from what I've read in this thread,
chromium-browser has a reactive team behind it).
/me just trying to avoid post-release comments like «Debian doesn't even
have chromium», unless there's a valid technical reason we can offer
to users.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
