Using the good old RPM Package Manager (RPM) where the installation failed due to failed dependencies.
$ sudo rpm -ivh google-chrome-stable_current_x86_64.rpm [sudo] password for ang: warning: google-chrome-stable_current_x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY error: Failed dependencies: lsb >= 4.0 is needed by google-chrome-stable-41.0.2272.118-1.x86_64 libXss.so.1()(64bit) is needed by google-chrome-stable-41.0.2272.118-1.x86_64
Instead of searching for the package names of the dependencies, we can use the yum localinstall command to resolve that for us. Unfortunately, the yum command has been delegated to dnf where the localinstall command does not exists.
$ sudo yum localinstall google-chrome-stable_current_x86_64.rpm Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. To transfer transaction metadata from yum to DNF, run 'dnf migrate'Redirecting to '/usr/bin/dnf localinstall google-chrome-stable_current_x86_64.rpm' No such command: localinstall. Please use /usr/bin/dnf --help It could be a DNF plugin command.
Hence, we use the dnf command directly. I'm still puzzle why we need 122 packages just to install Google Chrome. Most likely the dependencies of the LSB packages and all the Perl libraries.
$ sudo dnf install ./google-chrome-stable_current_x86_64.rpm ...... Transaction Summary ================================================================================= Install 122 Packages Total size: 66 M Total download size: 21 M Installed size: 245 M Is this ok [y/N]:
I still prefer YUM over DNF due to my familiarity with YUM instead of DNF. However, both are still lacking behind the apt-get despite DNF trying its best to narrow the gap.