Where Does Mercurial Install Loads Of

And its a very flexible tool thats ideal whether youre a lone programmer working on a small project, or part of a huge team dealing with thousands of files.

Mercurial permits a countless variety of development and collaboration methods, and this book offers several concrete suggestions to get you started.

This guide will help you: Learn the basics of working with a repository, changesets, and revisions Merge changes from separate repositories Set up Mercurial to work with files on a daily basis, including which ones to track Get examples and tools for setting up various workflow models Manage a project thats making progress on multiple fronts at once Find and fix mistakes by isolating problem sources Use hooks to perform actions automatically in response to repository events Customize the output of Mercurial Mercurial: The Definitive Guide maintains a strong focus on simplicity to help you learn Mercurial quickly and thoroughly.

All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.

Woo Now, when I figure out some good ways to accomplish my offline-commit workflow, Ill let you know;).

What I like about Subversion is that there is a central line of development.

This is great for teams because it forces them to integrate their code often.

This is great for open source projects because the users have one place to go to get the source; there is one version of the truth.

Its nice to have an experimental work space where I can create private branches all day and all night but you can do this in Subversion too.

Experimental work branches are dangerous if they do not get integrated with mainline development often.

DCVS lets you maintain mirrors of projects, potentially with your own patches to the project.

While this is convenient, I also put this in the dangerous category because the last thing I want is for someone to say, yeah my Django patch wasnt accepted and probably never will be, so just use my clone of the repository This is an integration nightmare.

This was instigated by the work a colleague of mine, Augie Fackler, is doing on the hg subversion extension.

You clone the repository locally and work within it as a Mercurial repository.

When you are ready, you push your changes back up to the central Subversion server.

You dont need a dev version of Mercurial and the easiest way to do everything is just through ports.

Then you can skip all the way down to the section about Activating hgsubversion.

To use hg subversion, you have to build the Subversion bindings and a ton of crap and you have to use the development version of hg.

The README file in hg subversion has more general instructions and there are also some useful instructions here.

Even though I use the Framework build of Python, the path of least resistance for me was to let macports do all the compiling.

Where Does Mercurial Install Loads Of

This will install loads of stuff, including python2.4 (for asciidoc), and python2.5.

If you had subversion 1.4 installed from ports you will need to deactivate that before installing the 1.5 port.

Dont do that. Next, I double checked that everything went smoothly.

Note that I had to set the PYTHONPATH for subversion bindings.

Next I went into the hg source and edited the Makefile, changing the vars at the top so that they pointed to my macport python install (I got prefix by running optlocalbinpython2.5 -c import sys; print sys.prefix ).

I got two errors, one with test-hgweb and one relating to bz2 archival.

Note again that I had to set the PYTHONPATH for subversion bindings.

I also added the svn-python2.5 path to my PYTHONPATH in.bashprofile.

And added optlocalLibraryFrameworksPython.frameworkVersions2.5bin (or optlocalbin if you install hg from ports) to my PATH so that the new hg is available.

Be careful to put this at the end of PATH if like me you prefer the official Framework.

Where Does Mercurial For Mac Install