Break config_default into master_site_configs.

masters/master.chromium.chrome/master.cfg

Index: masters/master.chromium.chrome/master.cfg
diff --git a/masters/master.chromium.chrome/master.cfg b/masters/master.chromium.chrome/master.cfg
index 9fa28a5770c7d81875518bc8772f4d9b1d75ed07..9cd786b885b78569f72bc307e58f17e0d0b8699c 100644
--- a/masters/master.chromium.chrome/master.cfg
+++ b/masters/master.chromium.chrome/master.cfg
@@ -14,8 +14,9 @@ from master.factory import chromium_factory
 
 # These modules come from scripts/common, which must be in the PYTHONPATH.
 import config

[Isaac (away), 2013/04/29 01:27:57]

This existing master_site_configs (like master.chromium.linux) extend from
Object instead of from a config base class.  But since the new ones extend from
config, do we need to refer to the config module directly rather than through
ActiveMaster object?

[agable, 2013/04/29 17:40:20]

The existing master_site_configs have been changed to inherit from config base
classes. That said, the master_site_configs do "from config import Master", so
we can't actually access config through them. In the spirit of having this
change be as minimally invasive as possible, I'd rather leave the 'import
configs' here, and fix those later when I move Archive and DatabaseSetup out of
config.

+import master_site_config
 
-ActiveMaster = config.Master.ChromiumChrome
+ActiveMaster = master_site_config.ChromiumChrome
 
 # This is the dictionary that the buildmaster pays attention to. We also use
 # a shorter alias to save typing.