LMConfig modularization

While modularization would be generally desirable for datasources, for configsources, it is a must.  I have looked at the code and it is very long, and effectively must be hands off to regular folk until there is builtin support for merging changes.  I would like to see the core components moved to libraries (with git or similar builtin for branch/merge handling) to allow for easier customization and code re-use.  Even simple changes, like "add a section with output from 'show interface status err-disabled'" would lead to unmanageable branching from the distributed code.

Thanks,
Mark