Another question: why to keep every module in separate repo? will it be easier to have them under one root?
Stephen Deasey wrote: > On Fri, May 23, 2008 at 8:45 PM, Vlad Seryakov <[EMAIL PROTECTED]> wrote: >> I am personally ready to switch right away, i use hg for xine-lib for a >> long time already, in readonly mode but it did not require much learning >> to use it. >> >> More questions, is hg repo hosted by SF? Is it Sf service or you just >> run additional hg server there? > > > I basically followed this recipe: > > http://www.selenic.com/mercurial/wiki/index.cgi/MercurialOnSourceforge > > Although I used mercurial-1.0 (installed into > /home/groups/n/na/naviserver/local/mercurial-1.0) > > All the repos live in /home/groups/n/na/naviserver/hg > > Mercurial comes with cgi-scripts to publish the repos, that's what you > see when you go to: > > http://naviserver.sourceforge.net/hg/ > > (See: /home/groups/n/na/naviserver/cgi-bin) > > (And btw. you can get the same view on your own machine by typing 'hg > serve', built-in web server). > > > So, the repos in $SF/hg are basically identical to what you end up > with on your own machine when you clone. The only difference is that I > modified the per-repo hgrc file to add the hooks for commit messages > and a couple of other small things. > > I guess I should make clear, the naviserver repo, and each of the > module repos would in fact be individual repos. > > > So to convert the other modules from cvs, you'd run 'hg convert' > (which you have to enable first, it's an extension shipped with > mercurial). And then you'd clean it up a little, make sure the commit > messages follow the mercurial style etc. And then you'd clone it up > there: > > hg clone ./nsexample ssh://sf/ns/hg/nsexample > > And then you would ssh into sf and copy the hgrc from an existing repo > into the new one: > > ssh sf > cd ~/ns/hg > cp naviserver/.hg/hgrc nsexample/.hg/hgrc > vi nsexample > > It should show up in the web interface automatically. You only need > to edit the top of the file to change the display name, basically just > this: > > [web] > description = Programmable Web Server > > [cia] > module = naviserver > > You could also edit 'contact' if you like. It's just for display on > the web interface. > > > That should be it. We can go into more details about how to convert > modules from cvs later, but shout out if you're keen to get started. > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
