On 16 February 2014 @11:10 zulu, Giorgio Bersano wrote:
Student: "Can we run Chrome?" Me: "Well, in his farsighted view Google decided it is uninterested to have it running on the prominent linux enterprise distribution. It worked in the past but after version 31 they made it impossible to build.
Actually, that's not accurate... "Chrome" installs just fine using Richard Lloyd's install_chrome.sh script.
The script from http://chrome.richardlloyd.org.uk/ downloads that package from a fedora 15 repo (getting it from fedora 16 or newer causes other errors/crashes), segregates it in /opt/google/chrome/lib so all other programs use the package from the CentOS repo, installs the Google-Chrome repo, fetches the latest stable release Chrome rpm and installs Chrome.
From then on, yum should install updates from the Google-Chrome repo (at least that's how it's done it for me since I used an early version of it to install v28 on CentOS 6.4 after I saw his post in https://www.centos.org/forums/viewtopic.php?t=6570 and yum's updated Chrome for me at least 6 times since then).
i.e. You've confused "Chrome" with "chromium"
As I recall, the Chrome rpm downloaded from Google's repo would fail to install with yum complaining about a new enough libstdc++ file not being available. I can't find on http://gcc.gnu.org/libstdc++/ what the difference is between the GLIBCXX_3.4.15 string offered by fedora15 and the older (GLIBCXX_3.4.12? GLIBCXX_3.4.13?) versions offered by CentOS 6.5, and don't understand why a minor revision like that would/could NOT be updated without waiting for RH/CentOS 7.x. But, then... I'm just a dumb electrician. :)