Yann Dirson wrote:
If we go this way, it could be a good idea to reorganize the vcpx
namespace at the same time, maybe moving those new classes to a
new vcpx.vcs namespace, maybe organized like this:
vcpx.vcs.git.core
vcpx.vcs.git.source
vcpx.vcs.git.target
Does it make sense ?
I took an intermediary direction, splitting the monolithic repository.py
into smaller units, under the vcpx.repository namespace. Now there is a
single place where a specific backend gets implemented:
vcpx.repository.xxx contains both the XxxRepository and the XxxWorkingDir.
I don't think that a more aggressive splitting would help, but I'm open
to further considerations. In a longer term plan, I'd like to move some
workingdir's behaviour on to the repository class (like, say,
"initializeRepository" and the like)...
ciao, lele.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
