Remove the enable_metro GYP flag, effectively making it on by default.

chrome/installer/mini_installer.gyp

Index: chrome/installer/mini_installer.gyp
diff --git a/chrome/installer/mini_installer.gyp b/chrome/installer/mini_installer.gyp
index e0980db6a46c341a97cc3fb89d66dbc063f6e582..1562b5f944c2064d9c0b9be4f89545fa9070086b 100644
--- a/chrome/installer/mini_installer.gyp
+++ b/chrome/installer/mini_installer.gyp
@@ -204,13 +204,13 @@
                     'enable_hidpi_flag': '',
                   },
                 }],
-                ['enable_metro == 1', {
+                ['enable_touch_ui == 1', {
                   'variables': {
-                    'enable_metro_flag': '--enable_metro=1',
+                    'enable_touch_ui_flag': '--enable_touch_ui=1',

[sky, 2012/05/24 23:45:34]

I'm not familiar with the mini installer. Will this set --enable-touch-ui for
every one?

[Jói, 2012/05/25 10:30:18]

This will cause the assets needed for the touch layout to be included in the
installer for everyone.  The layout won't actually be displayed except when
running in Metro.

                   },
                 }, {
                   'variables': {
-                    'enable_metro_flag': '',
+                    'enable_touch_ui_flag': '',
                   },
                 }],
                 ['component == "shared_library"', {
@@ -249,7 +249,7 @@
                 '--input_file', '<(RULE_INPUT_PATH)',
                 '--resource_file_path', '<(INTERMEDIATE_DIR)/packed_files.rc',
                 '<(enable_hidpi_flag)',
-                '<(enable_metro_flag)',
+                '<(enable_touch_ui_flag)',
                 '<(component_build_flag)',
                 # TODO(sgk):  may just use environment variables
                 #'--distribution=$(CHROMIUM_BUILD)',