On Fri, May 23, 2008 at 9:50 PM, Vlad Seryakov <[EMAIL PROTECTED]> wrote: > Another question: why to keep every module in separate repo? > will it be easier to have them under one root?
No, they need to be separate repos. The reason is that unlike cvs hg is changeset based. There is one commit message that goes with the changes to a collection of files. They go together, like a transaction in a db. When you do a 'hg log' you get the commit message, user, date etc. for each changeset. If we put all the modules into one repo then it would be like have just one ChangeLog for everything, with all message mixed together. Also, things like tags are repo wide, and you don't really want to tag nsdbi with naviserver-4.99.2, and vice-versa. There is an extension call 'forrest' which is something like repos within repos. I don't know if it's needed though. To keep updated, you could just stick something like the following in cron: for repo in ~/in/ns/*-hg; do hg -R $repo pull done We could publish a shell script with a list of all modules, to bootstrap for those who want a copy of everything. Also, slightly related, I think we want to follow a repo-as-branch model. So no branches within repos. It's simpler. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
