On 18.08.2009 07:23, Steve Borho wrote: > Hi folks, > > I've rewritten the TortoiseHg build script in pure python and replaced > the previous forest based approach with subrepos. The resulting script > is able to build nightly, unstable, and release packages of Mercurial > and TortoiseHg (at least once some crew-stable patches make it onto > the hg mainline). > > Repository of build script: > http://bitbucket.org/tortoisehg/thg-winbuild >
I've started to look at this. Looking at: http://bitbucket.org/tortoisehg/thg-winbuild/src/tip/README.txt README.txt contains: > The most up to date version of this information can be > found on this repository's wiki: > http://bitbucket.org/tortoisehg/thg-winbuild/wiki/Home Why? Wouldn't it make a lot more sense to have that README.txt file most up to date? I would even say, let's refer to the tip revision of README.txt from the wiki page. So I can trust and follow that README.txt once I have a local clone of the thg-winbuild. I'd prefer not to have to look at the wiki page to be able to create an installer. Like that, I can do it offline, once I have a local clone (bitbucket.org down, no internet connection, etc...) In theory, instructions could even vary between different revisions of thg-winbuild. Side question: do you intend to have a stable branch on thg-winbuild? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
