X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=e5c1aeabc58837dde2d9ff0b152e11d1e912f920;hp=3808f0b9acad88e07a1962763057a4240ec7ab92;hb=a40ae391231accafda8e5bc3bf95954c51c9638e;hpb=ca2d80ce585a60bf1944e7540002f0157e4dd7dc diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 3808f0b9..e5c1aeab 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -5,10 +5,10 @@ - - - - + + + + @@ -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 @@ -128,13 +128,13 @@ Hal. The first step is to join the privoxy-devel mailing list. - You can submit your ideas or, even better, patches. Patches are best - submitted to the Sourceforge tracker set up for this purpose, but - can be sent to the list for review too. + You can submit your ideas or, even better, patches. + Patches can also be submitted to the + Sourceforge patch tracker. - 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. @@ -259,7 +265,7 @@ Hal. Note that near a major public release, we get more cautious. There is always the possibility to submit a patch to the patch + url="https://sourceforge.net/p/ijbswa/patches/">patch tracker instead. @@ -295,8 +301,8 @@ Hal. Alternately, proposed changes can be submitted as patches output by git format-patch to the privoxy-devel mailing list or alternatively to the patch tracker on Sourceforge: - - https://sourceforge.net/tracker/?group_id=11118&atid=311118. + + https://sourceforge.net/p/ijbswa/patches/. Then ask for peer review. @@ -2272,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. @@ -2306,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 @@ -2498,7 +2505,7 @@ for-privoxy-version=3.0.11 be reset to one if this is the first RPM for dist which is built from version X.Y.Z. Check the - file + file list if unsure. Else, it must be set to the highest already available RPM release number for that version plus one. @@ -2529,55 +2536,6 @@ for-privoxy-version=3.0.11 - OS/2 - - First, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then get the OS/2 Setup module: - - - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup - - - You will need a mix of development tools. - 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, - autoconf and sh tools. - The packaging takes place with WarpIN, available from various sources, including - its home page: xworkplace. - - - Change directory to the os2setup directory. - Edit the os2build.cmd file to set the final executable filename. - For example, - - - installExeName='privoxyos2_setup_X.Y.Z.exe' - - - Next, edit the IJB.wis file so the release number matches - in the PACKAGEID section: - - - PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z" - - - You're now ready to build. Run: - - - os2build - - - You will find the WarpIN-installable executable in the - ./files directory. Upload this anonymously to - uploads.sourceforge.net/incoming, create a release - for it, and you're done. Use the release notes and Change Log from the - source tarball package. - - - Solaris Login to Sourceforge's compilefarm via ssh: @@ -2858,7 +2816,7 @@ for-privoxy-version=3.0.11 announce mailing list, Subject: "Version X.Y.Z available for download". Be sure to include the - + download location, the release notes and the Changelog. Also, post an updated News item on the project page Sourceforge, and update the Home page and docs linked from the Home page (see below). Other news sites