On 11/25/2011 at 02:08 PM, in message <4ECF53F4.8020306@suse.de>, Ludwig Nussel
wrote: Sankar P wrote: Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome Are you saying we should encourage users to install [proprietary] binary rpms from random sites on the Internet? Or are you saying we should encourage Google to maintain their openSUSE packages in Factory/update repos ie make them easily available to users and conform to our packaging policies?
We definitely can ask Google to maintain their openSUSE specific rpm build in OBS. However I doubt if they will be ready to conform to our
policies etc. My suggestion was the former.
I agree that some may feel paranoid about installing binary rpm from a third party site. For most people, Google has a higher level of trust
random site. Also, people already install VLC player from 3rd
On Friday 25 November 2011 01:58:18 Sankar P wrote: packaging than some party site. I
personally don't feel paranoid about installing chrome from Google's site. So I gave that suggestion. I agree that it may not be suitable for all.
For example, Google's google talk voice RPM that chromium lets you install both silently registered their repository (to keep it up to date) and installed a cronjob to re-register their repository if you remove it, when I looked at its scripts last year. That deviates too far from acceptable behaviour, in my opinion. Will -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org