%general-entities; ]> $LastChangedBy$ $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 and Vim. &lfs78_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 Required Optional , (gpg2 with Python bindings), (with Python bindings), Bazaar, CVS, Docutils (required to build the documentation), pyflakes, pygments, and pyOpenSSL User Notes: Build Mercurial by issuing the following command: make build To build the documentation (requires Docutils), issue: make doc Running the test suite is optional. If some thest fails, it can be disabled. To test the results in the subdiretory tests/tmp, skipping failing tests, issue: cat > tests/blacklists/failed-tests << "EOF" # Test Failures test-convert-svn-source.t test-convert-hg-svn.t 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 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 --debug --tmpdir tmp \ test-convert-svn-source.t \ test-convert-hg-svn.t \ test-gpg.t && popd Normally, failures will be repeated. However, if you add the switch "--debug" before "--tmpdir", and run again, the failures are gone. Normally, from now on, there will be no more failure 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, 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> <your@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 A great majority of extensions are disabled by default. Run hg help extensions if you need to enable any, e.g. when investigating test failures, and use one of the configuration files to enable it. If you have installed the and you want Mercurial to use them, as the root user: install -v -d -m755 /etc/mercurial && cat > /etc/mercurial/hgrc << "EOF" [web] cacerts = /etc/ssl/ca-bundle.crt EOF Installed Programs Installed Libraries Installed Directories hg several internal modules under /usr/lib/python&python2-majorver;/site-packages/mercurial /etc/mercurial and /usr/lib/python&python2-majorver;/site-packages/{hgext,mercurial} Short Descriptions hg is the program file for mercurial. hg