Changeset de33b2a for general/prog/mercurial.xml
- Timestamp:
- 03/12/2020 09:24:44 AM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 6ea9f5b3
- Parents:
- 5ab87cfa
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/mercurial.xml
r5ab87cfa rde33b2a 30 30 <title>Introduction to Mercurial</title> 31 31 32 <para><application>Mercurial</application> is a distributed source control 33 management tool similar to <application>Git</application> and 34 <application>Bazaar</application>. <application>Mercurial</application> is 35 written in <application>Python</application> and is used by projects such as 36 Mozilla and Vim.</para> 32 <para> 33 <application>Mercurial</application> is a distributed source control 34 management tool similar to <application>Git</application> and 35 <application>Bazaar</application>. <application>Mercurial</application> 36 is written in <application>Python</application> and is used by projects 37 such as Mozilla and Vim. 38 </para> 37 39 38 40 &lfs91_checked; … … 41 43 <itemizedlist spacing="compact"> 42 44 <listitem> 43 <para>Download (HTTP): <ulink url="&mercurial-download-http;"/></para> 44 </listitem> 45 <listitem> 46 <para>Download (FTP): <ulink url="&mercurial-download-ftp;"/></para> 47 </listitem> 48 <listitem> 49 <para>Download MD5 sum: &mercurial-md5sum;</para> 50 </listitem> 51 <listitem> 52 <para>Download size: &mercurial-size;</para> 53 </listitem> 54 <listitem> 55 <para>Estimated disk space required: &mercurial-buildsize;</para> 56 </listitem> 57 <listitem> 58 <para>Estimated build time: &mercurial-time;</para> 45 <para> 46 Download (HTTP): <ulink url="&mercurial-download-http;"/> 47 </para> 48 </listitem> 49 <listitem> 50 <para> 51 Download (FTP): <ulink url="&mercurial-download-ftp;"/> 52 </para> 53 </listitem> 54 <listitem> 55 <para> 56 Download MD5 sum: &mercurial-md5sum; 57 </para> 58 </listitem> 59 <listitem> 60 <para> 61 Download size: &mercurial-size; 62 </para> 63 </listitem> 64 <listitem> 65 <para> 66 Estimated disk space required: &mercurial-buildsize; 67 </para> 68 </listitem> 69 <listitem> 70 <para> 71 Estimated build time: &mercurial-time; 72 </para> 59 73 </listitem> 60 74 </itemizedlist> … … 93 107 <!-- seems to have a development rust port --> 94 108 95 <para>Build <application>Mercurial</application> by issuing the following 96 command:</para> 109 <para> 110 Build <application>Mercurial</application> by issuing the following 111 command: 112 </para> 97 113 98 114 <screen><userinput>make build</userinput></screen> 99 115 100 <para>To build the documentation (requires <xref linkend="docutils"/>), 101 issue:</para> 116 <para> 117 To build the documentation (requires <xref linkend="docutils"/>), issue: 118 </para> 102 119 103 120 <screen remap="doc"><userinput>2to3 -w doc/hgmanpage.py && 104 121 PYTHON=python3 make doc</userinput></screen> 105 122 106 <!-- All tests pass (or are skipped) at version 3.8.2107 <para>Running the test suite is optional. Tests which fail may be disabled,108 adding each one to <filename>tests/blacklists/failed-tests</filename>. In109 order to execute the test suite using the temporary directory <filename110 class="directory">tests/tmp</filename> and skipping the failing tests,111 issue:</para>112 113 Version 5.2.1 had one failure test-bundle2-exchange.t114 115 116 <screen remap="test"><userinput>cat > tests/blacklists/failed-tests << "EOF"117 <literal># Test Failures118 test-gpg.t</literal>119 EOF120 -->121 123 <para> 122 124 To run the test suite, issue: … … 127 129 of tests/blacklists, but do not include the makefile. --> 128 130 129 <para>where <replaceable><N></replaceable> is an integer between one 130 and the number of ( processor X threads ), inclusive. In order to 131 investigate any apparently failing tests, you may use the 132 <command>run-tests.py</command> script. To see the almost forty switches, 133 some of them very useful, issue <command>tests/run-tests.py 134 --help</command>. Running the following commands, you will execute only 135 the tests that failed before:</para> 131 <para> 132 where <replaceable><N></replaceable> is an integer between one 133 and the number of ( processor X threads ), inclusive. In order to 134 investigate any apparently failing tests, you may use the 135 <command>run-tests.py</command> script. To see the almost forty switches, 136 some of them very useful, issue <command>tests/run-tests.py 137 --help</command>. Running the following commands, you will execute only 138 the tests that failed before: 139 </para> 136 140 137 141 <screen remap="test"><userinput>pushd tests && … … 140 144 popd</userinput></screen> 141 145 142 <para>Normally, the previous failures will be confirmed. However, if 143 you add the switch 144 "--debug" before "--tmpdir", and run again, some failures are gone, which 145 seems to be a problem with the test suite. If this happens, normally, from 146 now on, there will be no more such failures whether you use the debug switch 147 or not. Three tests, test-alias.t, test-install.t, and 148 test-bundle2-exchange.t (intermittently), are known to fail.</para> 149 150 <para>An interesting switch is "--time", which will generate at the end of 151 the test suite execution, a table with all executed tests and respective 152 start, end, user, system and real times. Note that the switches may be 153 used with <command>make check</command> by including them in the 154 <envar>TESTFLAGS</envar> environment variable.</para> 155 156 <para>Install <application>Mercurial</application> by running the following 157 command (as <systemitem class="username">root</systemitem>):</para> 146 <para> 147 Normally, the previous failures will be confirmed. However, if 148 you add the switch <option>--debug</option> before 149 <option>--tmpdir</option>, and run again, some failures are gone, which 150 seems to be a problem with the test suite. If this happens, normally, 151 from now on, there will be no more such failures whether you use the 152 debug switch or not. Three tests, test-alias.t, test-install.t, and 153 test-bundle2-exchange.t (intermittently), are known to fail. 154 </para> 155 156 <para> 157 An interesting switch is <option>--time</option>, which will generate at 158 the end of the test suite execution, a table with all executed tests and 159 respective start, end, user, system and real times. Note that the 160 switches may be used with <command>make check</command> by including 161 them in the <envar>TESTFLAGS</envar> environment variable. 162 </para> 163 164 <para> 165 Install <application>Mercurial</application> by running the following 166 command (as <systemitem class="username">root</systemitem>): 167 </para> 158 168 159 169 <screen role="root"><userinput>make PREFIX=/usr install-bin</userinput></screen> 160 170 161 <para>If you built the documentation, install it by running the following 162 command (as <systemitem class="username">root</systemitem>):</para> 171 <para> 172 If you built the documentation, install it by running the following 173 command (as <systemitem class="username">root</systemitem>): 174 </para> 163 175 164 176 <screen role="root" 165 177 remap="doc"><userinput>make PREFIX=/usr install-doc</userinput></screen> 166 178 167 <para>After installation, two very quick and simple tests should run 168 correctly. The first one needs some configuration:</para> 179 <para> 180 After installation, two very quick and simple tests should run 181 correctly. The first one needs some configuration: 182 </para> 169 183 170 184 <screen><userinput>cat >> ~/.hgrc << "EOF" … … 173 187 EOF</userinput></screen> 174 188 175 <para>where you must replace <user_name> and <your@mail> (mail 176 is optional and can be omitted). With the user identity defined, run 177 <command>hg debuginstall</command> and several lines will be displayed, 178 the last one reading "no problems detected". Another quick and simple test 179 is just <command>hg</command>, which should output basic commands that can 180 be used with <command>hg</command>.</para> 189 <para> 190 where you must replace <user_name> and <your@mail> (mail 191 is optional and can be omitted). With the user identity defined, run 192 <command>hg debuginstall</command> and several lines will be displayed, 193 the last one reading "no problems detected". Another quick and simple 194 test is just <command>hg</command>, which should output basic commands 195 that can be used with <command>hg</command>. 196 </para> 181 197 182 198 </sect2> … … 211 227 </indexterm> 212 228 213 <para>The great majority of extensions are disabled by default. Run 214 <command>hg help extensions</command> if you need to enable any, e.g. 215 when investigating test failures. You will obtain the lists of enabled and 216 disabled extensions, and more information, such as how to enable or 217 disable them using configuration files.</para> 218 219 <para>If you have installed <xref linkend="make-ca"/> and want 220 <application>Mercurial</application> to use them, as the <systemitem 221 class="username">root</systemitem> user, issue:</para> 229 <para> 230 The great majority of extensions are disabled by default. Run 231 <command>hg help extensions</command> if you need to enable any, e.g. 232 when investigating test failures. You will obtain the lists of enabled 233 and disabled extensions, and more information, such as how to enable 234 or disable them using configuration files. 235 </para> 236 237 <para> 238 If you have installed <xref linkend="make-ca"/> and want 239 <application>Mercurial</application> to use them, as the <systemitem 240 class="username">root</systemitem> user, issue: 241 </para> 222 242 223 243 <screen role="root"><userinput>install -v -d -m755 /etc/mercurial && … … 262 282 <term><command>hg</command></term> 263 283 <listitem> 264 <para>is the mercurial version control system.</para> 284 <para> 285 is the mercurial version control system. 286 </para> 265 287 <indexterm zone="mercurial hg"> 266 288 <primary sortas="b-hg">hg</primary>
Note:
See TracChangeset
for help on using the changeset viewer.