Mercurial_ The Definitive Guide - Bryan O'Sullivan [117]
The Series File
The series file contains a list of the names of all patches that MQ can apply. It is represented as a list of names, with one name saved per line. Leading and trailing whitespace in each line is ignored.
Lines may contain comments. A comment begins with the # character, and extends to the end of the line. Empty lines, and lines that contain only comments, are ignored.
You will often need to edit the series file by hand, hence the support for comments and empty lines noted above. For example, you can comment out a patch temporarily, and qpush will skip over that patch when applying patches. You can also change the order in which patches are applied by reordering their entries in the series file.
Placing the series file under revision control is also supported; it is a good idea to place all of the patches that it refers to under revision control, as well. If you create a patch directory using the -c option to qinit, this will be done for you automatically.
The Status File
The status file contains the names and changeset hashes of all patches that MQ currently has applied. Unlike the series file, this file is not intended for editing. You should not place this file under revision control, or modify it in any way. It is used by MQ strictly for internal bookkeeping.
Appendix C. Installing Mercurial from Source
On a Unix-Like System
If you are using a Unix-like system that has a sufficiently recent version of Python (2.3 or newer) available, it is easy to install Mercurial from source. Here’s how:
Download a recent source tarball from http://www.selenic.com/mercurial/download.
Unpack the tarball:gzip -dc mercurial-MYVERSION.tar.gz | tar xf -
Go into the source directory and run the installer script. This will build Mercurial and install it in your home directory.cd mercurial-MYVERSION
python setup.py install --force --home=$HOME
Once the install finishes, Mercurial will be in the bin subdirectory of your home directory. Don’t forget to make sure that this directory is present in your shell’s search path.
You will probably need to set the PYTHONPATH environment variable so that the Mercurial executable can find the rest of the Mercurial packages. For example, on my laptop, I have set it to /home/bos/lib/python. The exact path that you will need to use depends on how Python was built for your system, but should be easy to figure out. If you’re uncertain, look through the output of the installer script above, and see where the contents of the mercurial directory were installed to.
On Windows
Building and installing Mercurial on Windows requires a variety of tools, a fair amount of technical knowledge, and considerable patience. I very much do not recommend this route if you are a “casual user.” Unless you intend to hack on Mercurial, I strongly suggest that you use a binary package instead.
If you are intent on building Mercurial from source on Windows, follow the “hard way” directions on the Mercurial wiki at http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall, and expect the process to involve a lot of fiddly work.
Appendix D. Open Publication License
Version 1.0, 8 June 1999
Requirements on Both Unmodified and Modified Versions
The Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction.
Proper form for an incorporation by reference is as follows:
Copyright (c) year by author’s name or designee. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vx.y or later (the latest version is presently available at http://www.opencontent.org/openpub/).
The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see License Options).