File/Directory Structure to facilitate svn:externals

Hi there.

I was wondering whether it would be possible, in a future release, to re-arrange the file/directory structure to make it possible to take better advantage of svn:externals. This would make my development of carts more productive and efficient (I suppose that sounds selfish... ;) ).

It would be really useful if includes/configure.php and admin/includes/configure.php could each live in their own directories, with nothing else in said directories. This would allow me to have one main zen-cart directory containing the latest release (I keep that in my own svn repository, making upgrading it very simple, and also taking care of any "oh, bugger, I didn't mean to overwrite that" moments) in a directory, and then I could use svn:externals to create and maintain the configure.php directories. This would allow me to swap in and out different shops' configurations, so I can easily be up and running with one or another shop without needing to remember where I left that client's build. Note: An svn:external is a directory, not a specific file (unfortunately, in this case).

It would also be exceptionally useful, come to think of it, if the files and directories that make up a template could be entirely self-contained within one directory, for the same benefit...