Mercurial-3.7.3

Introduction to Mercurial

Mercurial is a distributed source control management tool similar to Git and Bazaar. Mercurial is written in Python and is used by projects such as Mozilla and Vim.

This package is known to build and work properly using an LFS-7.9 platform.

Package Information

Mercurial Dependencies

Required

Python-2.7.11

Optional

git-2.8.0, GnuPG-2.1.11 (gpg2 with Python bindings), Subversion-1.9.4 (with Python bindings), Bazaar, CVS, Docutils (required to build the documentation), pyflakes, pygments, and pyOpenSSL

User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/mercurial

Installation of Mercurial

Build Mercurial by issuing the following command:

make build

To build the documentation (requires Docutils), issue:

make doc

Running the test suite is optional. Tests which fail may be disabled, adding each one to tests/blacklists/failed-tests. In order to execute the test suite using the temporary directory tests/tmp and skipping the failing tests, issue:

cat > tests/blacklists/failed-tests << "EOF"
# Test Failures
  test-gpg.t
EOF

rm -rf tests/tmp &&

TESTFLAGS="-j<N> --tmpdir tmp --blacklist blacklists/failed-tests" \
make check

where <N> is an integer between one and the number of ( processor X threads ), inclusive. In order to investigate the apparently failing tests, you may use the run-tests.py script. To see the almost forty switches, some of them very useful, issue tests/run-tests.py --help. Running the following commands, you will execute only the tests that failed before:

pushd tests  &&
  rm -rf tmp &&

  ./run-tests.py --tmpdir tmp test-gpg.t &&
popd

Normally, the previous failures will be confirmed. However, if you add the switch "--debug" before "--tmpdir", and run again, some failures are gone, which seems to be a problem with the test suite. If this happens, normally, from now on, there will be no more such failures whether you use the debug switch or not.

An interesting switch is "--time", which will generate at the end of the test suite execution, a table with all executed tests and respective start, end, user, system and real times. Notice that the switches may be used with make check, including them in the TESTFLAGS environment variable.

Install Mercurial by running the following command (as root):

make PREFIX=/usr install-bin

If you built the documentation, install it by running the following command (as root):

make PREFIX=/usr install-doc

After installed, two very quick and simple tests should run correctly. First one needs some configuration:

cat >> ~/.hgrc << "EOF"
[ui]
username = <user_name> <user@mail>
EOF

where you must replace <user_name> and <your@mail> (mail is optional and can be omitted). With the user identity defined, run hg debuginstall and several lines will be displayed, the last one reading "no problems detected". Another quick and simple test is just hg, which should output basic commands that can be used with hg.

Configuring Mercurial

Config Files

/etc/mercurial/hgrc and ~/.hgrc

The great majority of extensions are disabled by default. Run hg help extensions if you need to enable any, e.g. when investigating test failures. You will obtain the lists of enabled and disabled extensions, and more information, such as how to enable or disable them using configuration files.

If you have installed the Certificate Authority Certificates and want Mercurial to use them, as the root user, issue:

install -v -d -m755 /etc/mercurial &&
cat >> /etc/mercurial/hgrc << "EOF"
[web]
cacerts = /etc/ssl/ca-bundle.crt
EOF

Contents

Installed Programs: hg
Installed Libraries: several internal modules under /usr/lib/python2.7/site-packages/mercurial
Installed Directories: /etc/mercurial and /usr/lib/python2.7/site-packages/{hgext,mercurial}

Short Descriptions

hg

is the program file for mercurial.

Last updated on 2016-04-04 14:22:43 -0500