4
4
<title>The Source Code Repository</title>
5
5
6
6
<para>
7
- The <productname>PostgreSQL</productname> source code is stored and managed using the
8
- <productname>Git</productname> version control system. An public mirror of this
9
- is available and updated within a minute of the master repository.
7
+ The <productname>PostgreSQL</productname> source code is stored and managed
8
+ using the <productname>Git</productname> version control system. A public
9
+ mirror of the master repository is available; it is updated within a minute
10
+ of any change to the master repository.
10
11
</para>
11
12
12
13
<para>
13
14
Our wiki, <ulink
14
15
url="http://wiki.postgresql.org/wiki/Working_with_Git"></ulink>,
15
- has additional details on working with Git.
16
+ has some discussion on working with Git.
16
17
</para>
17
18
18
19
<para>
19
20
Note that building <productname>PostgreSQL</productname> from the source
20
- repository requires reasonably up-to-date versions of <application>bison</>
21
- and <application>flex </>. These tools are not needed to build from a
22
- distribution tarball since their output is included in the file.
23
- You will need Perl as well, but otherwise the tool requirements are the
24
- same .
21
+ repository requires reasonably up-to-date versions of <application>bison</>,
22
+ <application>flex</>, and <application>Perl </>. These tools are not needed
23
+ to build from a distribution tarball since the files they are used to build
24
+ are included in the tarball. Other tool requirements are the same as shown
25
+ in <xref linkend="installation"> .
25
26
</para>
26
27
27
28
<sect1 id="git">
28
29
<title>Getting The Source Via <productname>Git</></title>
29
30
30
31
<para>
31
32
With <productname>Git</> you will make a copy of the entire code repository
32
- to your local machine, so you will have access to all history and branches
33
+ on your local machine, so you will have access to all history and branches
33
34
offline. This is the fastest and most flexible way to develop or test
34
35
patches.
35
36
</para>
39
40
40
41
<step>
41
42
<para>
42
- You will need an installed version of <productname>Git</>, which you can get
43
- from <ulink url="http://git-scm.com"></ulink>. Many systems also have a recent
44
- version of <application>Git</> installed by default, or available in their
45
- package repository system.
43
+ You will need an installed version of <productname>Git</>, which you can
44
+ get from <ulink url="http://git-scm.com"></ulink>. Many systems already
45
+ have a recent version of <application>Git</> installed by default, or
46
+ available in their package distribution system.
46
47
</para>
47
48
</step>
48
49
49
50
<step>
50
51
<para>
51
- To being using the Git repository, make a clone of the official mirror:
52
+ To begin using the Git repository, make a clone of the official mirror:
52
53
53
54
<programlisting>
54
55
git clone git://git.postgresql.org/git/postgresql.git
55
56
</programlisting>
56
57
57
58
This will copy the full repository to your local machine, so it may take
58
59
a while to complete, especially if you have a slow Internet connection.
60
+ The files will be placed in a new subdirectory <filename>postgresql</> of
61
+ your current directory.
59
62
</para>
60
63
61
64
<para>
62
- The Git mirror can also be reached via the HTTP protocol in case for example
63
- a firewall is blocking access to the Git protocol. Just replace the URL
64
- like :
65
+ The Git mirror can also be reached via the HTTP protocol, if for example
66
+ a firewall is blocking access to the Git protocol. Just change the URL
67
+ prefix to <literal>http</>, as in :
65
68
66
69
<programlisting>
67
70
git clone http://git.postgresql.org/git/postgresql.git
@@ -83,10 +86,11 @@ git fetch
83
86
</para>
84
87
</step>
85
88
</procedure>
89
+
86
90
<para>
87
91
<productname>Git</> can do a lot more things than just fetch the source. For
88
- more information, consult the man pages for the product , or the website at
89
- <ulink url="http://git-scm.com"></>.
92
+ more information, consult the <productname>Git</> man pages, or see the
93
+ website at <ulink url="http://git-scm.com"></>.
90
94
</para>
91
95
</sect1>
92
96
0 commit comments