rootninja

The Google Repository

You can just go to http://www.google.com/chrome and download the rpm directly, but you’re probably going to need some dependencies, depending on what packages you already have on your system of course. So I think it’s easier just to setup the google repo and fetch it all at once.

$ sudo vi /etc/yum.repos.d/google.repo

[google]
name=Google - i386
baseurl=http://dl.google.com/linux/rpm/stable/i386
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub

[google-chrome]
name=google-chrome
baseurl=http://dl.google.com/linux/rpm/stable/i386
enabled=1
gpgcheck=1

$ sudo yum install google-chrome-beta

$ sudo tail -n 40 /var/log/yum.log
Updated: sqlite-3.6.20-1.fc12.x86_64
Installed: at-3.1.10-39.fc12.x86_64
Installed: pax-3.4-10.fc12.x86_64
nspr-4.8.2-1.fc12.i686
Updated: nss-util-3.12.5-1.fc12.1.x86_64
Installed: nss-util-3.12.5-1.fc12.1.i686
Installed: nss-3.12.4-14.fc12.i686
Installed: ncurses-libs-5.7-3.20090207.fc12.i686
Installed: readline-6.0-3.fc12.i686
Installed: sqlite-3.6.20-1.fc12.i686
Installed: alsa-lib-1.0.21-3.fc12.i686
Installed: foomatic-db-filesystem-4.0-6.20090819.fc12.noarch
Installed: foomatic-db-ppds-4.0-6.20090819.fc12.noarch
Installed: foomatic-db-4.0-6.20090819.fc12.noarch
Installed: foomatic-4.0.3-1.fc12.x86_64
Installed: redhat-lsb-3.2-7.fc12.x86_64
Installed: google-chrome-beta-4.0.249.30-33928.i386

Done. Launch it via “google-chrome” or from the gnome toolbar.

That’s it for installing on Fedora 12. If you’re looking for Fedora 10 or Fedora 11, try these links:
* http://devcraft.wordpress.com/2009/08/27/how-to-install-chromium-or-google-chrome-in-fedora-11/
* http://rajaseelan.com/2009/07/04/how-to-install-google-chrome-in-fedora-10-or-fedora-11/

$ man google-chrome

NAME
       google-chrome - the web browser from Google

SYNOPSIS
       google-chrome [OPTION] [PATH|URL]

DESCRIPTION
       See the Google Chrome help center for help on using the browser.

              <http://www.google.com/support/chrome/>

       This manpage only describes invocation, environment, and arguments.

OPTIONS
       Google  Chrome  has  hundreds of undocumented command-line flags that
       are added and removed at the whim of the developers.  Here, we  docu-
       ment relatively stable flags.

       --user-data-dir=DIR
              Specifies  the  directory  that  user data (your "profile") is
              kept in.  Defaults to ~/.config/google-chrome/Default .  Sepa-
              rate  instances  of  Google Chrome must use separate user data
              directories; repeated invocations of google-chrome will  reuse
              an existing process for a given user data directory.

       --app=URL
              Runs URL in "app mode": with no browser toolbars.

       --proxy-server=host:port
              Specify  the  HTTP/HTTPS proxy server.  Overrides any environ-
              ment variables or settings picked via the options dialog.

       --no-proxy-server
              Disables the proxy server.  Overrides  any  environment  vari-
              ables or settings picked via the options dialog.

       --proxy-auto-detect
              Autodetect  proxy  configuration.   Overrides  any environment
              variables or settings picked via the options dialog.

       --proxy-pac-url=URL
              Specify proxy autoconfiguration URL.  Overrides  any  environ-
              ment variables or settings picked via the options dialog.

       As a GTK+ app, Google Chrome also obeys GTK+ command-line flags, such
       as --display.  See the GTK documentation for more:

              <http://library.gnome.org/devel/gtk/stable/gtk-running.html>
              <http://library.gnome.org/devel/gtk/stable/gtk-x11.html>

ENVIRONMENT
       Google Chrome obeys the following environment variables:
       all_proxy
              Shorthand  for  specifying  all  of  http_proxy,  https_proxy,
              ftp_proxy

       http_proxy, https_proxy, ftp_proxy
              The proxy servers  used  for  HTTP,  HTTPS,  and  FTP.   Note:
              because  Gnome/KDE  proxy  settings  may  propagate into these
              variables in some terminals,  this  variable  is  ignored  (in
              preference  for  actual  system  proxy  settings) when running
              under Gnome or KDE.  Use the command-line flags to  set  these
              when you want to force their values.

       auto_proxy
              Specify  proxy  autoconfiguration.   Defined and empty autode-
              tects; otherwise, it should be an  autoconfig  URL.   But  see
              above note about Gnome/KDE.

FILES
       ~/.config/google-chrome
              Default directory for configuration data.

       ~/.cache/google-chrome
              Default  directory  for  cache data.  (Why?  See <http://stan-
              dards.freedesktop.org/basedir-spec/latest/> .)

BUGS
       Bug tracker:

              http://code.google.com/p/chromium/issues/list

       Be sure to do your search within "All Issues" before reporting  bugs,
       and  be sure to pick the "Defect on Linux" template when filing a new
       one.

AUTHOR
       The Chromium team - <http://www.chromium.org></verbatim>