rev |
line source |
bos@559
|
1 <!-- vim: set filetype=docbkxml shiftwidth=2 autoindent expandtab tw=77 : -->
|
bos@85
|
2
|
bos@559
|
3 <appendix id="chap:srcinstall">
|
bos@572
|
4 <?dbhtml filename="installing-mercurial-from-source.html"?>
|
bos@559
|
5 <title>Installing Mercurial from source</title>
|
bos@85
|
6
|
bos@559
|
7 <sect1 id="sec:srcinstall:unixlike">
|
bos@559
|
8 <title>On a Unix-like system</title>
|
bos@85
|
9
|
bos@559
|
10 <para>If you are using a Unix-like system that has a sufficiently
|
bos@559
|
11 recent version of Python (2.3 or newer) available, it is easy to
|
bos@559
|
12 install Mercurial from source.</para>
|
bos@559
|
13 <orderedlist>
|
bos@559
|
14 <listitem><para>Download a recent source tarball from <ulink
|
bos@559
|
15 url="http://www.selenic.com/mercurial/download">http://www.selenic.com/mercurial/download</ulink>.</para>
|
bos@559
|
16 </listitem>
|
bos@559
|
17 <listitem><para>Unpack the tarball:</para>
|
bos@559
|
18 <programlisting>gzip -dc mercurial-MYVERSION.tar.gz | tar xf -</programlisting>
|
bos@559
|
19 </listitem>
|
bos@559
|
20 <listitem><para>Go into the source directory and run the
|
bos@559
|
21 installer script. This will build Mercurial and install it
|
bos@559
|
22 in your home directory.</para>
|
bos@559
|
23 <programlisting>cd mercurial-MYVERSION
|
bos@559
|
24 python setup.py install --force --home=$HOME</programlisting>
|
bos@559
|
25 </listitem>
|
bos@559
|
26 </orderedlist>
|
bos@559
|
27 <para>Once the install finishes, Mercurial will be in the
|
bos@559
|
28 <literal>bin</literal> subdirectory of your home directory.
|
bos@559
|
29 Don't forget to make sure that this directory is present in your
|
bos@559
|
30 shell's search path.</para>
|
bos@85
|
31
|
bos@559
|
32 <para>You will probably need to set the <envar>PYTHONPATH</envar>
|
bos@559
|
33 environment variable so that the Mercurial executable can find
|
bos@559
|
34 the rest of the Mercurial packages. For example, on my laptop,
|
bos@559
|
35 I have set it to <literal>/home/bos/lib/python</literal>. The
|
bos@559
|
36 exact path that you will need to use depends on how Python was
|
bos@559
|
37 built for your system, but should be easy to figure out. If
|
bos@559
|
38 you're uncertain, look through the output of the installer
|
bos@559
|
39 script above, and see where the contents of the
|
bos@559
|
40 <literal>mercurial</literal> directory were installed to.</para>
|
bos@85
|
41
|
bos@559
|
42 </sect1>
|
bos@559
|
43 <sect1>
|
bos@559
|
44 <title>On Windows</title>
|
bos@85
|
45
|
bos@559
|
46 <para>Building and installing Mercurial on Windows requires a
|
bos@559
|
47 variety of tools, a fair amount of technical knowledge, and
|
bos@559
|
48 considerable patience. I very much <emphasis>do not
|
bos@559
|
49 recommend</emphasis> this route if you are a <quote>casual
|
bos@559
|
50 user</quote>. Unless you intend to hack on Mercurial, I
|
bos@559
|
51 strongly suggest that you use a binary package instead.</para>
|
bos@85
|
52
|
bos@559
|
53 <para>If you are intent on building Mercurial from source on
|
bos@559
|
54 Windows, follow the <quote>hard way</quote> directions on the
|
bos@559
|
55 Mercurial wiki at <ulink
|
bos@559
|
56 url="http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall">http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall</ulink>,
|
bos@559
|
57 and expect the process to involve a lot of fiddly work.</para>
|
bos@559
|
58
|
bos@559
|
59 </sect1>
|
bos@559
|
60 </appendix>
|
bos@559
|
61
|
bos@559
|
62 <!--
|
bos@559
|
63 local variables:
|
bos@559
|
64 sgml-parent-document: ("00book.xml" "book" "appendix")
|
bos@559
|
65 end:
|
bos@559
|
66 -->
|