%general-entities; ]> $Date$ 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 for Firefox and Thunderbird. &lfs111_checked; Package Information Download (HTTP): Download (FTP): Download MD5 sum: &mercurial-md5sum; Download size: &mercurial-size; Estimated disk space required: &mercurial-buildsize; Estimated build time: &mercurial-time; Mercurial Dependencies Optional (required to build the documentation), , (with Python bindings), (runtime, to access ssh://... repositories), , (see rust/README.rst and rust/rhg/README.md), (with Python bindings), Bazaar, CVS, pyflakes, pyOpenSSL, and re2 User Notes: Build Mercurial by issuing the following command: make build To build the documentation (requires ), issue: make doc To run the test suite, issue (8 tests are known to fail): TESTFLAGS="-j<N> --tmpdir tmp --blacklist blacklists/fsmonitor --blacklist blacklists/linux-vfat" make check where <N> is an integer between one and the number of ( processor X threads ), inclusive. In order to investigate any 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 reproducible. However, if you add the switch --debug before --tmpdir, and run the tests again, some failures may disappear, which is a problem with the test suite. If this happens, there will be no more of these failures even if you do not pass the --debug switch again. An interesting switch is --time, which will generate a table of all the executed tests and their respective start, end, user, system and real times once the tests are complete. Note that these switches may be used with make check by 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 installation, two very quick and simple tests should run correctly. The 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. /etc/mercurial/hgrc and ~/.hgrc /etc/mercurial/hgrc ~/.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. This will output a list of enabled and disabled extensions, as well as more information such as how to enable or disable extensions using configuration files. If you have installed and want Mercurial to use the certificates, as the root user, issue: install -v -d -m755 /etc/mercurial && cat > /etc/mercurial/hgrc << "EOF" [web] cacerts = /etc/pki/tls/certs/ca-bundle.crt EOF Installed Programs Installed Libraries Installed Directories hg several internal modules under /usr/lib/python&python3-majorver;/site-packages/mercurial /etc/mercurial and /usr/lib/python&python3-majorver;/site-packages/{hgdemandimport,hgext,hgext3rd,mercurial} Short Descriptions hg is the mercurial version control system hg