Remove legacy non-client-based geolocation code.

chrome/chrome_browser.gypi

Index: chrome/chrome_browser.gypi
diff --git a/chrome/chrome_browser.gypi b/chrome/chrome_browser.gypi
index 78907845385605bae0e6fbfd4a98232470382aee..615143e634d6591fa963e2484f33aef9fafbfd1b 100644
--- a/chrome/chrome_browser.gypi
+++ b/chrome/chrome_browser.gypi
@@ -4374,14 +4374,6 @@
             'browser/importer/nss_decryptor_system_nss.h',
           ],
         }],
-        # We are migrating to client-based geolocation. Once the migration
-        # has finished, ENABLE_CLIENT_BASED_GEOLOCATION will disappear.
-        # See bugs:
-        #     https://bugs.webkit.org/show_bug.cgi?id=45752 and
-        #     http://code.google.com/p/chromium/issues/detail?id=59907
-        ['"ENABLE_CLIENT_BASED_GEOLOCATION=1" in feature_defines', {
-          'defines': [ 'ENABLE_CLIENT_BASED_GEOLOCATION=1' ]

[bulach, 2011/01/05 10:12:29]

remember to coordinate with the sheriffs for a possible clobber..

[John Knottenbelt, 2011/01/05 12:01:31]

Will do, however, I don't think it will require a clobber. The flag will still
be defined when building WebKit (feature_overrides.gypi), but it will no longer
be defined in the Chrome sources as no source code there will depend on it. 

On 2011/01/05 10:12:29, bulach wrote:

-        }],
       ],
     },
     {