Using Mercurial during the development process
By user12820842 on Jul 29, 2008
With guidance from Anurag, I've been trying to figure out how the NWAM development process changes with the advent of Mercurial as the source code management tool for OpenSolaris. I've tried to detail the process I'm using here in case it's of use to others. The basic idea is to have a development repository in which we make changes (and will eventually push to the main NWAM repository on opensolaris.org), along with a build repository, to which we pull our changes to build/test. Here are the steps:
- clone a development repository
# hg clone ssh://email@example.com/hg/nwam/nwam1 /path2/dev_ws
- make changes by editing files
- commit these changes in the development repository
- clone/pull the above development changes to a build/test repository
# hg clone /path2/dev_ws /path2/build_wsTo ensure latest changes are there:
# cd /path2/build_ws # hg updateOr if rather than cloning, you need to update an existing build repository:
# cd /path2/build_ws # hg pull -u /path2/dev_ws
- clone usr/closed separately, adding it to build repository (external-to-Sun builds need to download the closed binaries at this point instead I believe).
# cd /path2/build_ws/usr # hg clone ssh://elpaso.sfbay//export/clone-hg/usr/closed
- push dev changes, replacing yourname with your opensolaris.org account name. SSH keys need to be set up with youro OpenSolaris account for this to work properly, and your account needs to be on the list of contributors.
# hg commit
# cd /path2/dev_ws # hg push ssh://firstname.lastname@example.org/hg/nwam/nwam1