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.
Download (HTTP): https://www.mercurial-scm.org/release/mercurial-3.7.1.tar.gz
Download MD5 sum: 4e922fcc9454d2665f20c3b9b4741add
Download size: 4.5 MB
Estimated disk space required: 54 MB (with documentation, 378 MB with docs and tests)
Estimated build time: less than 0.1 SBU (with documentation, 3.4 SBU with docs and tests, using -j8)
Build Mercurial by issuing the following command:
To build the documentation (requires Docutils), issue:
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-convert-svn-source.t test-convert-hg-svn.t test-gpg.tEOF rm -rf tests/tmp && TESTFLAGS="-j
<N>--tmpdir tmp --blacklist blacklists/failed-tests" \ make check
<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 scrypt. 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-convert-svn-source.t \ test-convert-hg-svn.t \ test-gpg.t && popd
Normally, the previous failures will be confirmed, except for "test-gpg.t" which now pass (this is weird!). 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 generated 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
make PREFIX=/usr install-bin
If you built the documentation, install it by running the following
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 =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.
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.crtEOF
Last updated on 2016-02-29 13:16:05 -0800