X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=6a0e72e8e639ac0a47b310756e0a265626ac9569;hb=61478413a02d7be37d44efb5c0c997a39a9da463;hp=cfd0f307eee88d15e58c9dfb3a38f28c0aaa6f70;hpb=6be4997a13c22c081656b1d3960e2e2ee4fac60f;p=privoxy.git
diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml
index cfd0f307..6a0e72e8 100644
--- a/doc/source/developer-manual.sgml
+++ b/doc/source/developer-manual.sgml
@@ -5,7 +5,7 @@
-
+
@@ -19,7 +19,7 @@
Purpose : developer manual
- Copyright (C) 2001-2018 Privoxy Developers https://www.privoxy.org/
+ Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
See LICENSE.
========================================================================
@@ -39,7 +39,7 @@
Copyright
- &my-copy; 2001-2018 by
+ &my-copy; 2001-2020 by
Privoxy Developers
@@ -133,8 +133,8 @@ Hal.
can be sent to the list for review too.
- You will also need to have a git package installed, which will
- entail having ssh installed as well, in order to access the git repository.
+ You will also need to have a git package installed,
+ in order to access the git repository.
Having the GNU build tools is also going to be important (particularly,
autoconf and gmake).
@@ -158,10 +158,16 @@ Hal.
Access to Git
The project's Git repository is hosted at the
- Privoxy site.
- The Git repository URL is
- ssh://git@git.privoxy.org:23/git/privoxy.git,
- the central repository is called privoxy, and the
+ Privoxy website.
+ For Privoxy team members with push privileges the Git repository URL is
+ ssh://git@git.privoxy.org:23/git/privoxy.git.
+
+
+ Contributors without push privileges can
+ git clone https://www.privoxy.org/git/privoxy.git
.
+
+
+ The central repository is called privoxy, and the
source branch is called master. Subfolders exist
within the project for target-dependent build and packaging tools, each
including the name of the target operating system in their name (e.g.
@@ -2233,9 +2239,10 @@ for-privoxy-version=3.0.11
All documentation should be rebuilt:
+ $ make man
$ make dok
+ $ make dok-man
$ make dok-tidy
- $ make man
$ make config-file
Finished docs should be then be committed to Git (for those
@@ -2271,7 +2278,7 @@ for-privoxy-version=3.0.11
Tag all files in Git with the version number with
- cvs tag v_X_Y_Z
.
+ git tag v_X_Y_Z
.
Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.
@@ -2305,8 +2312,9 @@ for-privoxy-version=3.0.11
mkdir dist # delete or choose different name if it already exists
cd dist
- cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
- cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
+ git clone https://www.privoxy.org/git/privoxy.git
+ cd privoxy
+ git checkout v_X_Y_Z
@@ -2542,7 +2550,7 @@ for-privoxy-version=3.0.11
The main compilation takes place with IBM Visual Age C++.
Some ancillary work takes place with GNU tools, available from
various sources like hobbes.nmsu.edu.
- Specificially, you will need autoheader,
+ Specifically, you will need autoheader,
autoconf and sh tools.
The packaging takes place with WarpIN, available from various sources, including
its home page: xworkplace.