Cause mini_installer tests to noop on component builds.

chrome/installer/mini_installer/configuration.h

Index: chrome/installer/mini_installer/configuration.h
diff --git a/chrome/installer/mini_installer/configuration.h b/chrome/installer/mini_installer/configuration.h
index fb955ad10131ff54b2de9e84933c25b4ffe66ebf..2e108c7be2b61205a7697b6db5f2d903b5437baf 100644
--- a/chrome/installer/mini_installer/configuration.h
+++ b/chrome/installer/mini_installer/configuration.h
@@ -55,6 +55,11 @@ class Configuration {
   // Returns true if --system-level is on the command line.
   bool is_system_level() const { return is_system_level_; }
 
+  // Returns true if --query-component-build is on the command line.
+  // This will cause mini_installer to exit and return 1 if this is

[grt (UTC plus 2), 2014/05/28 18:51:44]

my brain is about to 'splode. 0 exit code means success, so the query should
return 0 for a component install and non-zero for false. but this looks backward
when you look at the python. what to do? personally, i would have gone the other
way, but i can see the logic in doing it this way. oh well.

[robertshield, 2014/05/28 21:27:30]

Yeah, I chewed on that for a bit too, but 1 = yes, 0 = no seemed (just
marginally) more reasonable.

+  // a component install or 0 otherwise.
+  bool query_component_build() const { return query_component_build_; }
+
  protected:
   void Clear();
   bool InitializeFromCommandLine(const wchar_t* command_line);
@@ -69,6 +74,7 @@ class Configuration {
   bool has_app_host_;
   bool is_multi_install_;
   bool is_system_level_;
+  bool query_component_build_;
 
  private:
   Configuration(const Configuration&);