2009/1/5 Steve Borho <[email protected]> > On Mon, Jan 5, 2009 at 1:27 PM, Peer Sommerlund <[email protected] > > wrote: > >> TK has the secret recipe for thg 0.5 (and 0.6, I assume) >> >> >> I'm working on something which tastes a little more of distutil / >> setuptools, which also replaces the MQ with a forest based system. >> >> See http://www.bitbucket.org/peso/thg-distutils-build/ >> >> In case anybody feels like joining this they are more than welcome. >> > > I'm wondering if a hybrid approach would be a good idea. > > 1) clone mercurial-stable > 2) pull tortoisehg history and merge > 3) pull qct history and merge > 4) create small patch queue to fix up remaining bits > > This *uber* repository would be short-lived, only used for building the > installer. > Only the small patch queue is maintained from release-to-release. All > development > would still happen on the individual repositories. >
I had some trouble getting the patch queue to work, partly because it took some time understanding that the mq patched the mercurial repository to build the THG installer. So, I'm trying to come up with a process that does not use patches, as I feel that patches is less easy to maintain and troubleshoot. Less magic means lesser spirits (like me) can join the fun. Once the patch queue is replaced by a build script, there is no need to merge repositories. Regards, Peer
------------------------------------------------------------------------------
_______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
