Directly import the only thing we ever use here
Use layering config parser
Looks like debugging to me
Tuple unpacking
Booleans are already booleans...
Let shutit tell you where a config item was last set
Don't hit disk for overrides, give then a name in cfg history
No reason to use print_config here
Use RawConfigParser to make life easier for layers
Cowardly work around possible issues
Merge pull request #79 from aidanhs/aphs-tracking-config-parser

Let sc action show where a config item has actually come from