]>
Commit | Line | Data |
---|---|---|
c538d2d3 LT |
1 | |
2 | Git installation | |
3 | ||
4 | Normally you can just do "make" followed by "make install", and that | |
5 | will install the git programs in your own ~/bin/ directory. If you want | |
6 | to do a global install, you can do | |
7 | ||
eff351c9 BF |
8 | $ make prefix=/usr all doc ;# as yourself |
9 | # make prefix=/usr install install-doc ;# as root | |
c538d2d3 | 10 | |
c44922a7 JH |
11 | (or prefix=/usr/local, of course). Just like any program suite |
12 | that uses $prefix, the built results have some paths encoded, | |
13 | which are derived from $prefix, so "make all; make prefix=/usr | |
14 | install" would not work. | |
c538d2d3 | 15 | |
55667714 JN |
16 | Alternatively you can use autoconf generated ./configure script to |
17 | set up install paths (via config.mak.autogen), so you can write instead | |
18 | ||
3900145e | 19 | $ make configure ;# as yourself |
55667714 JN |
20 | $ ./configure --prefix=/usr ;# as yourself |
21 | $ make all doc ;# as yourself | |
22 | # make install install-doc ;# as root | |
23 | ||
24 | ||
c538d2d3 LT |
25 | Issues of note: |
26 | ||
27 | - git normally installs a helper script wrapper called "git", which | |
28 | conflicts with a similarly named "GNU interactive tools" program. | |
29 | ||
30 | Tough. Either don't use the wrapper script, or delete the old GNU | |
31 | interactive tools. None of the core git stuff needs the wrapper, | |
32 | it's just a convenient shorthand and while it is documented in some | |
215a7ad1 | 33 | places, you can always replace "git commit" with "git-commit" |
c538d2d3 LT |
34 | instead. |
35 | ||
36 | But let's face it, most of us don't have GNU interactive tools, and | |
37 | even if we had it, we wouldn't know what it does. I don't think it | |
38 | has been actively developed since 1997, and people have moved over to | |
39 | graphical file managers. | |
40 | ||
3c767a08 JH |
41 | - You can use git after building but without installing if you |
42 | wanted to. Various git commands need to find other git | |
43 | commands and scripts to do their work, so you would need to | |
44 | arrange a few environment variables to tell them that their | |
45 | friends will be found in your built source area instead of at | |
46 | their standard installation area. Something like this works | |
47 | for me: | |
48 | ||
49 | GIT_EXEC_PATH=`pwd` | |
50 | PATH=`pwd`:$PATH | |
f7661ce0 | 51 | GITPERLLIB=`pwd`/perl/blib/lib |
6fcca938 | 52 | export GIT_EXEC_PATH PATH GITPERLLIB |
3c767a08 | 53 | |
c538d2d3 LT |
54 | - Git is reasonably self-sufficient, but does depend on a few external |
55 | programs and libraries: | |
56 | ||
57 | - "zlib", the compression library. Git won't build without it. | |
58 | ||
59 | - "openssl". The git-rev-list program uses bignum support from | |
60 | openssl, and unless you specify otherwise, you'll also get the | |
61 | SHA1 library from here. | |
62 | ||
63 | If you don't have openssl, you can use one of the SHA1 libraries | |
64 | that come with git (git includes the one from Mozilla, and has | |
765ac8ec | 65 | its own PowerPC and ARM optimized ones too - see the Makefile). |
c538d2d3 | 66 | |
215a7ad1 JH |
67 | - "libcurl" and "curl" executable. git-http-fetch and |
68 | git-fetch use them. If you do not use http | |
addf88e4 | 69 | transfer, you are probably OK if you do not have |
99cff830 | 70 | them. |
c538d2d3 | 71 | |
3402f1d6 JH |
72 | - expat library; git-http-push uses it for remote lock |
73 | management over DAV. Similar to "curl" above, this is optional. | |
74 | ||
addf88e4 | 75 | - "wish", the Tcl/Tk windowing shell is used in gitk to show the |
663a5ed5 HB |
76 | history graphically |
77 | ||
78 | - "ssh" is used to push and pull over the net | |
3cab3594 JH |
79 | |
80 | - "perl" and POSIX-compliant shells are needed to use most of | |
81 | the barebone Porcelainish scripts. | |
82 | ||
3cab3594 JH |
83 | - Some platform specific issues are dealt with Makefile rules, |
84 | but depending on your specific installation, you may not | |
85 | have all the libraries/tools needed, or you may have | |
86 | necessary libraries at unusual locations. Please look at the | |
87 | top of the Makefile to see what can be adjusted for your needs. | |
cd8c4589 JR |
88 | You can place local settings in config.mak and the Makefile |
89 | will include them. Note that config.mak is not distributed; | |
90 | the name is reserved for local settings. | |
eff351c9 BF |
91 | |
92 | - To build and install documentation suite, you need to have the | |
93 | asciidoc/xmlto toolchain. Alternatively, pre-formatted | |
94 | documentation are available in "html" and "man" branches of the git | |
95 | repository itself. For example, you could: | |
96 | ||
97 | $ mkdir manual && cd manual | |
98 | $ git init-db | |
efc7fa53 | 99 | $ git fetch-pack git://git.kernel.org/pub/scm/git/git.git man html | |
eff351c9 BF |
100 | while read a b |
101 | do | |
102 | echo $a >.git/$b | |
103 | done | |
104 | $ cp .git/refs/heads/man .git/refs/heads/master | |
105 | $ git checkout | |
106 | ||
107 | to checkout the pre-built man pages. Also in this repository: | |
108 | ||
109 | $ git checkout html | |
110 | ||
111 | would instead give you a copy of what you see at: | |
112 | ||
113 | http://www.kernel.org/pub/software/scm/git/docs/ | |
114 |