1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Installing from GIT
===================
Last update: Feb 2, 2014
GIT (http://git-scm.com/) is the recommended way to track the
development, especially if you plan to maintain a modified version or
want to submit patches.
Downloading
-----------
First, download the SWI-Prolog source using git. This takes a while the
first time, but subsequent updates will be fast:
% git clone https://github.com/SWI-Prolog/swipl-devel.git
After cloning the main repository, you have to fetch generated files and
Prolog packages that are distributed as separate git submodules. This is
done with the script `prepare`. The `prepare` script requires `curl` and
GNU `autoconf`.
% cd swipl-devel
% ./prepare
If this step completed successfully, you are at the same point as after
downloading the sources as a tarball and unpacking.
Next, continue as described in INSTALL
Submitting a patch
------------------
GIT shines for structured handling of distributed development. If you
want to submit a patch, use git-format-patch to create the content of an
e-mail message. Depending on the nature, send the patch to the
SWI-Prolog mailinglist or bugs@swi-prolog.org.
Updating
--------
If you made no branches and patches, you update to the latest using
% make distclean
% git pull
% ./prepare
% ./build (see using of the build script in INSTALL.notes)
If you have patches, this is slightly more difficult. You can keep your
history clean using this instead of the simple pull above:
% make distclean
% git checkout master
% git pull
% git checkout my-branch
% git rebase master
% ./prepare
% ./build
Submitting patches
------------------
Please consult http://www.swi-prolog.org/howto/SubmitPatch.html if you
want to submit patches. By default, try to get modifications and patches
accepted in the main source because:
1. It simplifies updating for you
2. Your patch will be kept consistent with the rest of the source
3. Other users may improve or fix your patch
4. You can become famous
5. Other users will profit too
|
