I see that I could get the Chrome browser directly from Google, but am I going to be able to install it via yum any time soon?
I see that I could get the Chrome browser directly from Google, but am I going to be able to install it via yum any time soon?
Have you seen repos.fedorapeople.org?
Registered Linux User #348347
Have you been seduced by siduction? http://siduction.org/index.php
Running Fedora 19/20, siduction and openSUSE 13.1 with KDE
I had not!
And there is one there that looks like it should work.
I'll have to explore some of the other repos there too.
Every time I look there seems to be more interesting things stored there. Glad you found what you were looking for.
Registered Linux User #348347
Have you been seduced by siduction? http://siduction.org/index.php
Running Fedora 19/20, siduction and openSUSE 13.1 with KDE
Huh? Google Chrome has been available as an rpm from their website for a good while now. Even the beta and devel versions have rpm's available. The rpm's also install a .repo file to keep them updated.
Keep in mind that the version on fedora people is a sometimes updated version of chromium and is not the same as the google package.
the simple way is to download google chrome packaged in rpm format. the run the command below as root:when you successfully install the chrome, the repository is also installed for google-chrome.Code:yum localinstall package_path
then, when you want to update your chrome browser in future, just run:hope this can be helpful!Code:yum update google-chrome
yum localinstall failed:But installing directly with rpm worked:Code:warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 7fac5991: NOKEY Public key for google-chrome-stable_current_x86_64.rpm is not installedCode:sudo rpm -i google-chrome-stable_current_x86_64.rpm
Here is how you install Google Chrome with yum
32bit version:
yum localinstall --nogpgcheck -y https://dl.google.com/linux/direct/g...rrent_i386.rpm
64bit version
yum localinstall --nogpgcheck -y https://dl.google.com/linux/direct/g...ent_x86_64.rpm
I don't like this. The --nogpgcheck switch discards protection.
There are lots of people who register domains that are just 1 letter different than a well-known domain so they can capture you when you make an error typing in the well-known domain. Some of these are evil-doers that intend to scam the innocent.
Suppose some reprobate packaged an RPM full of malware and named it the same, but at their slightly different URL. They can't sign it with Google's secret key, so if you have Google's public key and you check the signature, you would catch it and avoid a lot of grief. But with --nogpgcheck, you would become a victim.
The Linux world has been spared all manner of viruses and other malware largely, I believe, because of GPG signing.
You can get the Google gpg key like so, as root:
Or just follow the directions from their websiteCode:rpm --import https://dl-ssl.google.com/linux/linux_signing_key.pub
Last edited by PabloTwo; 6th February 2012 at 04:12 AM.
All the install from Google does is add the google-chrome repo, mark Chrome to be installed, and activate the package manager. Once installed it behaves no differently than if you had used yum. Well, aside from the fact that it still auto-updates itself, but I don't think there's any way to install Chrome without that.
For references: Chromium and Google Chrome not the same at all. You can think if Chromium as "Google Chrome with less", since it removes all proprietary code, particularly the PDF viewer and Flash.
downloading chrome from the website seems more faster than from the repository
Last edited by oliveryty; 6th February 2012 at 04:36 AM.
The point of using the repository is so I can keep it updated with no extra effort beyond what I normally do to update my system. That is, once in a while I run "sudo yum update" and voila!
BTW, I installed google-chrome-stable from the repository a while back and it now gets updated by yum along with everything else. Not that I use it very often, but it's installed.
And thank you, deanej. I had wondered about the difference between Chrome and Chromium, but never got around to looking into it. Now I'd like to know why Google named their browser after a key Mozilla component.