Chromium On CentOS 6
I have chromium installed on CentOS 7 and it works fine, I now need to install it on a CentOS 6 workstation. However, it is not available in EPEL as it is for C 7. From what I understand, this is because it is already available in a supplementary channel from RHEL for C 6.
Is this the recommended method for installing it on C 6?
https://www.tecmint.com/install-google-chrome-on-redhat-CentOS-fedora-linux/
11 thoughts on - Chromium On CentOS 6
Just curious – why are you using the epel, rather than google, release for CentOS-7?
The current google repo releases, (which install without any issues and work well on CentOS-7) are:
stable.x86_64 62.0.3202.94-1
beta.x86_64 63.0.3239.59-1
while the epel one is:
61.0.3163.100-1
which was the “google stable” release in late september, and is about five releases back.
We can’t build things from the supplemental channel in RHEL .. they normally have issues with licensing. In this case, it is the flash library that is not completely open for rebuilding.
Ah, good, so this would be using the google-chrome.repo? I was not familiar with it.
Yes, from the google chrome repository, using google-chrome.repo. The CentOS wiki page at:
<https://wiki.CentOS.org/AdditionalResources/Repositories/GoogleYumRepos>
has the details if you need them. This works for -7, not -6.
And for CentOS 6?
OK, I have no interest in Flash, however.
familiar
Wasn’t the latest Google Chrome unsupported on CentOS 6 because of some dependency problems or some such?
Sorin,
Indeed, CentOS 6 is not longer officially supported by Chrome. It hasn’t been for a few years, though there are workarounds[1].
It’s high time people migrated to EL7.
[1] – http://li.nux.ro/download/nux/dextop/el6/x86_64/chrome-deps-stable-3.11-1.x86_64.rpm
been
That was indeed my main incentive to upgrade to CentOS 7!
If not for Chrome, I’d have stayed on C6 till 2020.
Hi,
If you don’t mind installing singularity
(https://github.com/singularityware/singularity), you can run a CentOS-7 docker based container with google-chrome at the expense of disk space.
If you have version >= 2.4 installed you can just do something like:
$ mkdir ~/home-for-google-chrome
$ singularity run -B /run -H ~/home-for-google-chrome \
shub://truatpasteurdotfr/singularity-docker-CentOS7-google-chrome
caveat: works for me, and google-chrome is running with –no-sandbox
Cheers
Tru PS: https://github.com/truatpasteurdotfr/singularity-docker-CentOS7-google-chrome
Am 28.11.2017 um 12:29 schrieb Tru Huynh:
Is it not easier to rebuild for example the EPEL7 package [1]? Did anyone tried it?
I have something like
$ scl enable devtoolset-${X} rpmbuild chromium.spec
in mind. The difficult part will be the exact examination of the needed toolchain! Some kind of reconstruction of the build process that upstream is applying every couple of weeks for packaging the last stable version [2].
Here some (old) resources:
– https://github.com/hughesjr/chromium_el_builder
– Some efforts have been made at NCSU. From there following sentence [3]:
So, what is upstream exactly doing to get the build done? Do we need an SIG :-)
[1] http://mirror.us.leaseweb.net/epel/7/SRPMS/Packages/c/chromium-61.0.3163.100-1.el7.src.rpm
[2] $ curl -s “https://omahaproxy.appspot.com/all?csv=1” |grep -E “linux,stable” |cut -d”,” -f3
[3] http://install.linux.ncsu.edu/pub/yum/itecs/public/chromium/howto/readme.txt