X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=da62dadefc141bf84f12aa0e9a8c4594c216952b;hp=1376edcf4854b7c664d1cf9f1c666c03ecc6c8f0;hb=372e9f40a2d5fe2ef6d381b2e37a7cd7bd13dc2a;hpb=c854049f3f2062748a25f1d57e96b78bd93578e0 diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 1376edcf..da62dade 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -5,10 +5,7 @@ - - - - + @@ -18,15 +15,11 @@ ]> - Copyright &my-copy; 2001-2009 by - Privoxy Developers + Copyright + &my-copy; 2001-2020 by + Privoxy Developers - - $Id: developer-manual.sgml,v 2.48 2012/03/20 13:05:39 fabiankeil Exp $ - - - @@ -138,16 +127,16 @@ Hal. Quickstart to Privoxy Development The first step is to join the developer's mailing list. - You can submit your ideas, or even better patches. Patches are best + url="https://lists.privoxy.org/mailman/listinfo/privoxy-devel">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 will also need to have a cvs package installed, which will - entail having ssh installed as well (which seems to be a requirement of - SourceForge), in order to access the cvs repository. Having the GNU build - tools is also going to be important (particularly, autoconf and gmake). + 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). For the time being (read, this section is under construction), you can @@ -158,37 +147,46 @@ Hal. - The CVS Repository + The Git Repository If you become part of the active development team, you will eventually - need write access to our holy grail, the CVS repository. One of the + need write access to our holy grail, the Git repository. One of the team members will need to set this up for you. Please read - this chapter completely before accessing via CVS. + this chapter completely before accessing via Git. - Access to CVS + Access to Git + + The project's Git repository is hosted at 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 project's CVS repository is hosted on - SourceForge. - Please refer to the chapters 6 and 7 in - SF's site - documentation for the technical access details for your - operating system. For historical reasons, the CVS server is - called ijbswa.cvs.sourceforge.net, the repository is - called ijbswa, and the source tree module is called - current. + 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. + Windows, OSXPackageBuilder, debian). There is a webview of the Git + hierarchy at + + https://www.privoxy.org/gitweb/?p=privoxy.git;a=tree, + which might help with visualizing how these pieces fit together. - + Branches - Within the CVS repository, there are modules and branches. As - mentioned, the sources are in the current - module. Other modules are present for platform specific - issues. There is a webview of the CVS hierarchy at http://ijbswa.cvs.sourceforge.net/ijbswa/, - which might help with visualizing how these pieces fit together. + Whilst the central repository contains only the master branch, developers + are of course free to create branches in their local repositories as they + develop features, fixes, or update the target-dependent tools. Only once + such changes are fully tested ought they be pushed back to the central + repository master branch. - CVS Commit Guidelines + Git Commit Guidelines The source tree is the heart of every software project. Every effort must be made to ensure that it is readable, compilable and consistent at all times. We expect anyone with CVS access to strictly + main development trunk, and --> We expect anyone with Git access to strictly adhere to the following guidelines: Basic Guidelines, for all branches: - Please don't commit even @@ -261,19 +258,18 @@ Hal. If necessary, prepare the commit messages in advance. - Before changing things on CVS, make sure that your changes are in line + Before changing things on Git, make sure that your changes are in line with the team's general consensus on what should be done. 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/tracker/?atid=311118&group_id=11118&func=browse">patch tracker instead. - + + Writing Documentation Using DocBook - A Crash Course useful. @@ -511,7 +509,6 @@ Hal. Here it is: - @@ -522,21 +519,24 @@ Hal. Tags delimiting a block of text (even small blocks) should be on their own line. Like: + <para> Some text goes here. </para> - + + Tags marking individual words, or few words, should be in-line: + Just to <emphasis>emphasize</emphasis>, some text goes here. - - + Tags should be nested and step indented for block text like: (except in-line tags) + <para> <itemizedlist> @@ -547,7 +547,8 @@ Hal. </para> </itemizedlist> </para> - + + This makes it easier to find the text amongst the tags ;-) @@ -608,7 +609,6 @@ Hal. - @@ -640,7 +640,6 @@ Hal. custom entities are listed below. See any of the main docs for examples. - @@ -658,6 +657,7 @@ Hal. the finished doc at that point. + Commonly used internal entities: @@ -684,7 +684,6 @@ Hal. - There are others in various places that are defined for a specific purpose. Read the source! @@ -952,11 +951,9 @@ int ms_iis5_hack = 0; Instead of: - int msiis5hack = 0; int msIis5Hack = 0; - @@ -979,12 +976,10 @@ int load_some_file(struct client_state *csp) Instead of: - int loadsomefile(struct client_state *csp) int loadSomeFile(struct client_state *csp) - @@ -1003,13 +998,12 @@ int loadSomeFile(struct client_state *csp) (.h) extern int load_aclfile(struct client_state *csp); (.c) int load_aclfile(struct client_state *csp) - Instead of: + Instead of: (.h) extern int load_aclfile(struct client_state *); or (.h) extern int load_aclfile(); (.c) int load_aclfile(struct client_state *csp) - @@ -1061,7 +1055,6 @@ int loadSomeFile(struct client_state *csp) Instead of: - #define USE_IMG_LST 1 or #define _USE_IMAGE_LIST 1 or @@ -1069,7 +1062,6 @@ int loadSomeFile(struct client_state *csp) #define use_image_list 1 or #define UseImageList 1 - @@ -1470,12 +1462,10 @@ for (size_t cnt = 0; cnt < len; cnt++) Exception: - /* This is not a local include, but requires a path element. */ #include <sys/fileName.h> - Note: Please! do not add "-I." to the Makefile without a _very_ good reason. This duplicates the #include @@ -1801,15 +1791,14 @@ static void unload_re_filterfile(void *f) { ... } Example for file comments: -const char FILENAME_rcs[] = "$Id$"; /********************************************************************* * - * File : $Source$ + * File : $Source * * Purpose : (Fill me in with a good description!) * * Copyright : Written by and Copyright (C) 2001-2009 - * the Privoxy team. http://www.privoxy.org/ + * the Privoxy team. https://www.privoxy.org/ * * This program is free software; you can redistribute it * and/or modify it under the terms of the GNU General @@ -1841,7 +1830,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; Note: This declares the rcs variables that should be - added to the "show-proxy-args" page. If this is a brand new + added to the "show-version" page. If this is a brand new creation by you, you are free to change the "Copyright" section to represent the rights you wish to maintain. @@ -1855,15 +1844,14 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id$" /********************************************************************* * - * File : $Source$ + * File : $Source * * Purpose : (Fill me in with a good description!) * * Copyright : Written by and Copyright (C) 2001-2009 - * the Privoxy team. http://www.privoxy.org/ + * the Privoxy team. https://www.privoxy.org/ * * This program is free software; you can redistribute it * and/or modify it under the terms of the GNU General @@ -1954,13 +1942,14 @@ int FUNCTION_NAME(void *param1, const char *x) Testplan for releases Explain release numbers. major, minor. developer releases. etc. - + Remove any existing rpm with rpm -e Remove any file that was left over. This includes (but is not limited to) + /var/log/privoxy /etc/privoxy @@ -1968,7 +1957,7 @@ Remove any file that was left over. This includes (but is not limited to) /etc/init.d/privoxy /usr/doc/privoxy* - + Install the rpm. Any error messages? @@ -1978,26 +1967,72 @@ Install the rpm. Any error messages? Start browsing. Does Privoxy work? Logfile written? Remove the rpm. Any error messages? All files removed? - + - Test reports - -Please submit test reports only with the test form -at sourceforge. Three simple steps: - - - Select category: the distribution you test on. - Select group: the version of Privoxy that we are about to release. - Fill the Summary and Detailed Description with something - intelligent (keep it short and precise). - - - Do not mail to the mailing list (we cannot keep track on issues there). - + Fuzzing Privoxy + + To make fuzzing more convenient, Privoxy can be configured + with --enable-fuzz which will result in the --fuzz option + becoming available. + + + Example (tested on ElectroBSD): + + +# Compile Privoxy with instrumentation for afl +$ export CC=afl-clang +$ export CFLAGS="-fsanitize=address -ggdb" +$ export CPPFLAGS=-I/usr/local/include/ +$ export LDFLAGS="-fsanitize=address -L/usr/local/lib" +$ export AFL_USE_ASAN=1 +$ export AFL_HARDEN=1 +$ ./configure --with-debug --enable-extended-host-patterns --enable-accept-filter --enable-no-gifs --enable-compression --enable-strptime-sanity-checks --enable-external-filters --enable-fuzz + +$ ./privoxy --fuzz +Privoxy version 3.0.24 (http://www.privoxy.org/) +Usage: ./privoxy [--config-test] [--chroot] [--help] [--no-daemon] [--pidfile pidfile] [--pre-chroot-nslookup hostname] [--user user[.group]] [--version] [configfile] + ./privoxy --fuzz fuzz-mode ./path/to/fuzzed/input [--stfu] + +Supported fuzz modes and the expected input: + action: Text to parse as action file. + client-request: Client request to parse. Currently incomplete + client-header: Client header to parse. + chunked-transfer-encoding: Chunk-encoded data to dechunk. + deflate: deflate-compressed data to decompress. + filter: Text to parse as filter file. + gif: gif to deanimate. + gzip: gzip-compressed data to decompress. + pcrs-substitute: A pcrs-substitute to compile. Not a whole pcrs job! Example: Bla $1 bla C $3 blah. + server-header: Server header to parse. + server-response: Server response to parse. + +The following fuzz modes read data from stdin if the 'file' is '-' + client-request + client-header + chunked-transfer-encoding + deflate + gif + gzip + pcrs-substitute + server-header + server-response + +Aborting + +$ export ASAN_OPTIONS='abort_on_error=1' +$ mkdir input output +$ echo '$1 bla fasel $2' > input/pcrs +$ afl-fuzz -i input -o output -m none ~/git/privoxy/privoxy --fuzz pcrs-substitute - --stfu + +$ cat >input/pcrs.txt +FILTER: bla fasel +s@(.{1})[432](\d+)@$1$2$hostname@UgisT + +$ afl-fuzz -i input/ -o output/ -f bla.filter -m none privoxy --fuzz filter bla.filter --stfu + - @@ -2028,6 +2063,7 @@ at sourceforge. Three simple steps: First you need to determine which version number the release will have. Privoxy version numbers consist of three numbers, separated by dots, like in X.Y.Z (e.g. 3.0.0), where: + @@ -2040,6 +2076,7 @@ at sourceforge. Three simple steps: + Y, the version minor, represents the branch within the major version. At any point in time, there are two branches being maintained: The stable branch, with an even minor, say, 2N, in which no functionality is @@ -2057,13 +2094,15 @@ at sourceforge. Three simple steps: Z, the point or sub version, represents a release of the software within a branch. - It is therefore incremented immediately before each code freeze. + It is therefore incremented immediately after each software release. + The point version is reset to zero when the minor changes. @@ -2079,9 +2118,8 @@ at sourceforge. Three simple steps: - - In summary, the main CVS trunk is the development branch where new + In summary, the main Git trunk is the development branch where new features are being worked on for the next stable series. This should almost always be where the most activity takes place. There is always at least one stable branch from the trunk, e.g now it is @@ -2098,7 +2136,7 @@ at sourceforge. Three simple steps: Developers should remember too that if they commit a bugfix to the stable branch, this will more than likely require a separate submission to the - main trunk, since these are separate development trees within CVS. If you + main trunk, since these are separate development trees within Git. If you are working on both, then this would require at least two separate check outs (i.e main trunk, and the stable release branch, which is v_3_0_branch at the moment). @@ -2107,55 +2145,120 @@ at sourceforge. Three simple steps: - Before the Release: Freeze + Before the Release The following must be done by one of the developers prior to each new release. - - - - + + + Make sure that everybody who has worked on the code in the last couple of days has had a chance to yell no! in case they have pending changes/fixes in their pipelines. Announce the freeze so that nobody will interfere with last minute changes. - + - Increment the version number (point from odd to even in development - branches!) in configure.in. (RPM spec files - will need to be incremented as well.) + Update the code status (CODE_STATUS="xxx") in configure.in to one of + "alpha", "beta" or "stable". - If default.action has changed since last - release (i.e. software release or standalone actions file release), - bump up its version info to A.B in this line: + Rebuild configure and GNUMakefile to make sure the updated values are being used. + + +$ autoheader && autoconf # rebuild configure +$ ./configure # rebuild GNUmakefile + + + + make dok-release to update the sgml documentation source files. + + + + + If action file processing has changed and is not backward-compatible, + make sure the "for-privoxy-version=x.y.z" minimum version number in + default.action.master has been updated: + - {+add-header{X-Actions-File-Version: A.B} -filter -no-popups} +{{settings}} +############################################################################# +#MASTER# COMMENT: The minimum Privoxy version: +for-privoxy-version=3.0.11 + + + + Create the change log: + + $ git tag + # to see the tags + $ git log [last release tag]..HEAD > /tmp/log + # get the commit log since the last release + $ utils/makeChangeLog /tmp/log > /tmp/change.log + # reformat the commit log + + + Edit /tmp/change.log to remove trivial + changes and group the changes under general headings like: + + +- Bug fixes: +- Action file improvements: +- Filter file improvements: +- General improvements: +- Documentation improvements: +- Build system improvements: +- Code cleanups: +- Privoxy-Log-Parser: +- Privoxy-Regression-Test: + + + Add the contents of /tmp/change.log to the + start of ChangeLog and re-create + doc/source/changelog.sgml: + + + $ utils/changelog2doc.pl /tmp/change.log >| doc/source/changelog.sgml + + + - Then change the version info in doc/webserver/actions/index.php, - line: '$required_actions_file_version = "A.B";' + All developers should look at the ChangeLog and + make sure noteworthy changes are referenced. - All documentation should be rebuild after the version bump. - Finished docs should be then be committed to CVS (for those + All documentation should be rebuilt: + + $ make man + $ make dok + $ make dok-man + $ make dok-tidy + $ make config-file + + Finished docs should be then be committed to Git (for those without the ability to build these). Some docs may require rather obscure processing tools. config, - the man page (and the html version of the man page), and the PDF docs - fall in this category. REAMDE, the man page, AUTHORS, and config - should all also be committed to CVS for other packagers. The - formal docs should be uploaded to the webserver. See the - Section "Updating the webserver" in this manual for details. + the man page (and the html version of the man page) + fall in this category. README, the man page, AUTHORS, and config + should all also be committed to Git for other packagers. The + formal docs should be uploaded to the webserver. See the section + "Updating the webserver" + in this manual for details. + + + + + Commit all files that were changed in the above steps! @@ -2174,29 +2277,11 @@ at sourceforge. Three simple steps: - All developers should look at the ChangeLog and - make sure noteworthy changes are referenced. - - - - - Commit all files that were changed in the above steps! - - - - - Tag all files in CVS with the version number with - cvs tag v_X_Y_Z. + Tag all files in Git with the version number with + git tag v_X_Y_Z. Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc. - - - If the release was in a development branch, increase the point version - from even to odd (X.Y.(Z+1)) again in configure.in and - commit your change. - - On the webserver, copy the user manual to a new top-level directory @@ -2208,7 +2293,6 @@ at sourceforge. Three simple steps: - @@ -2221,22 +2305,21 @@ at sourceforge. Three simple steps: For all types of packages, including the source tarball, you must make sure that you build from clean sources by exporting - the right version from CVS into an empty directory (just press return when + the right version from Git into an empty directory (just press return when asked for a password): - 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 - Do NOT change a single bit, including, but not limited to - version information after export from CVS. This is to make sure that + version information after export from Git. This is to make sure that all release packages, and with them, all future bug reports, are based on exactly the same code. @@ -2264,7 +2347,6 @@ at sourceforge. Three simple steps: Please keep these general guidelines in mind when putting together your package. These apply to all platforms! - @@ -2325,7 +2407,7 @@ at sourceforge. Three simple steps: interest (and possibly renamed to index.html). This should be one level up from the manuals. There is a link also on this page to an HTMLized version of the man page. To avoid 404 for - this, it is in CVS as + this, it is in Git as doc/webserver/man-page/privoxy-man-page.html, and should be included along with the manuals. There is also a css stylesheets that can be included for better presentation: @@ -2373,7 +2455,6 @@ at sourceforge. Three simple steps: - @@ -2383,28 +2464,22 @@ at sourceforge. Three simple steps: version into an empty directory. (See "Building and releasing packages" above). Then run: - cd current autoheader && autoconf && ./configure - Then do: - make tarball-dist - To upload the package to Sourceforge, simply issue - make tarball-upload - Go to the displayed URL and release the file publicly on Sourceforge. For the change log field, use the relevant section of the @@ -2423,42 +2498,36 @@ at sourceforge. Three simple steps: packages" above). - As the only exception to not changing anything after export from CVS, + As the only exception to not changing anything after export from Git, now examine the file privoxy-dist.spec and make sure that the version information and the RPM release number are correct. The RPM release numbers for each version start at one. Hence it must 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. Then run: - cd current autoheader && autoconf && ./configure - Then do - make dist-dist - To upload the package to Sourceforge, simply issue - make dist-upload rpm_packagerev - where rpm_packagerev is the RPM release number as determined above. @@ -2473,11 +2542,9 @@ at sourceforge. Three simple steps: 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++. @@ -2493,28 +2560,22 @@ at sourceforge. Three simple steps: 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 @@ -2528,31 +2589,25 @@ at sourceforge. Three simple steps: Login to Sourceforge's compilefarm via ssh: - ssh cf.sourceforge.net - Choose the right operating system (not the Debian one). When logged in, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run: - cd current autoheader && autoconf && ./configure - Then run - gmake solaris-dist - which creates a gzip'ed tar archive. Sadly, you cannot use make solaris-upload on the Sourceforge machine (no ncftpput). You now have @@ -2562,37 +2617,50 @@ at sourceforge. Three simple steps: - Windows + Windows + - You should ensure you have the latest version of Cygwin (from - http://www.cygwin.com/). - Run the following commands from within a Cygwin bash shell. + Note that the docbook generated files might need some hand editing, + so the Windows build makefile does not rebuild the docs. + First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing - packages" above). Then get the Windows setup module: - - - - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co winsetup - + packages" above). + Then you can build the package. This is fully automated, and is - controlled by winsetup/GNUmakefile. + controlled by windows/GNUmakefile. All you need to do is: - - cd winsetup + cd windows make - Now you can manually rename privoxy_setup.exe to - privoxy_setup_X_Y_Z.exe, and upload it to - SourceForge. When releasing the package on SourceForge, use the release notes + privoxy_setup_X.Y.Z.exe, and the build + directory to privoxy_X.Y.Z. + Create a .zip file of the newly renamed privoxy_X.Y.Z directory, + GPG sign the installer and zip file, + + + $ gpg --armor --detach --sign privoxy_setup_X.Y.Z.exe + $ gpg --armor --detach --sign privoxy_X.Y.Z.zip + + + and upload the files to SourceForge. + + + + When releasing the package on SourceForge, use the release notes and Change Log from the source tarball package. @@ -2605,30 +2673,24 @@ at sourceforge. Three simple steps: entry to debian/changelog, if it is not already there, for example by running: - debchange -v &p-version;-&p-status;-1 "New upstream version" - Then, run: - dpkg-buildpackage -rfakeroot -us -uc -b - This will create ../privoxy_&p-version;-&p-status;-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue - make debian-upload - Mac OS X @@ -2638,7 +2700,7 @@ at sourceforge. Three simple steps: packages" above). - There are three modules available in the CVS repository for use on Mac + There are three modules available in the Git repository for use on Mac OS X, though technically only two of them generate a release (the other can be used to install from source). @@ -2646,12 +2708,12 @@ at sourceforge. Three simple steps: OSXPackageBuilder module The OSXPackageBuilder module generates OS X installer packages - supporting all Macs running OS X 10.4 and above. Obtain it from CVS as + supporting all Macs running OS X 10.4 and above. Obtain it from Git as follows into a folder parallel to the exported privoxy source: + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder - The module contains complete instructions on its usage in the file OS X Package Builder HOWTO.txt. @@ -2673,21 +2735,19 @@ at sourceforge. Three simple steps: supports only Intel Macs running OS X 10.6 or higher. - Check out the module from CVS as follows into a folder parallel to the + Check out the module from Git as follows into a folder parallel to the exported privoxy source: + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup - Then run: - cd osxsetup build - This will run autoheader, autoconf and configure as well as make. @@ -2700,11 +2760,9 @@ at sourceforge. Three simple steps: package" button. If you specify ./Privoxy.pkg as the output package name, you can then create the distributable zip file with the command: - zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg - You can then upload this file directly to the Files section of the Sourceforge project in the Macintosh (OS X) folder. Each new version @@ -2721,15 +2779,15 @@ at sourceforge. Three simple steps: from source on a single machine. - Check out the module from CVS as follows into a folder parallel to the + Check out the module from Git as follows into a folder parallel to the exported privoxy source: + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup - The module contains complete instructions on its usage in its - README file. The end result will be the the + README file. The end result will be the exported version of Privoxy installed on the build machine. @@ -2737,111 +2795,8 @@ at sourceforge. Three simple steps: FreeBSD - Login to Sourceforge's compile-farm via ssh: - - - - ssh cf.sourceforge.net - - - - Choose the right operating system. - When logged in, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then run: - - - - cd current - autoheader && autoconf && ./configure - - - - Then run: - - - - gmake freebsd-dist - - - - which creates a gzip'ed tar archive. Sadly, you cannot use make - freebsd-upload on the Sourceforge machine (no ncftpput). You now have - to manually upload the archive to Sourceforge's ftp server and release - the file publicly. Use the release notes and Change Log from the - source tarball package. - - - - HP-UX 11 - - First, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then run: - - - - cd current - autoheader && autoconf && ./configure - - - - Then do FIXME. - - - - Amiga OS - - First, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then run: - - - - cd current - autoheader && autoconf && ./configure - - - - Then do FIXME. - - - - AIX - - Login to Sourceforge's compilefarm via ssh: - - - - ssh cf.sourceforge.net - - - - Choose the right operating system. - When logged in, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then run: - - - - cd current - autoheader && autoconf && ./configure - - - - Then run: - - - - make aix-dist - - - - which creates a gzip'ed tar archive. Sadly, you cannot use make - aix-upload on the Sourceforge machine (no ncftpput). You now have - to manually upload the archive to Sourceforge's ftp server and release - the file publicly. Use the release notes and Change Log from the - source tarball package. + Update the www/privoxy port and submit a diff upstream. + For details see the FreeBSD Porter's Handbook. @@ -2853,32 +2808,30 @@ at sourceforge. Three simple steps: to SourceForge, and go through the release steps. The upload is done via FTP: - - - - - Upload to: ftp://upload.sourceforge.net/incoming - - - - - user: anonymous - - - - - password: ijbswa-developers@lists.sourceforge.net - - - - + + + + Upload to: ftp://upload.sourceforge.net/incoming + + + + + user: anonymous + + + + + password: ijbswa-developers@lists.sourceforge.net + + + Or use the make targets as described above. - Once this done go to https://sourceforge.net/project/admin/editpackages.php?group_id=11118, + Once this done go to + + https://sourceforge.net/project/admin/editpackages.php?group_id=11118, making sure you are logged in. Find your target platform in the second column, and click Add Release. You will then need to create a new release for your package, using the format @@ -2908,15 +2861,44 @@ at sourceforge. Three simple steps: After the Release When all (or: most of the) packages have been uploaded and made available, - send an email to the announce - mailing list, Subject: "Version X.Y.Z available for download". Be sure to + send an email to the + 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 + + 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 and release oriented sites, such as Freshmeat, should also be notified. + + Then update the source code for the next version to be released: + + + + + Increment the version number and change the code status to "UNRELEASED" + in configure.in + + + + + Rebuild configure (autoheader && autoconf) + and GNUMakefile (./configure) + + + + + make dok-release to update the sgml documentation source files. + + + + + Commit all your changes. + + + + @@ -2933,16 +2915,13 @@ at sourceforge. Three simple steps: If you have changed anything in the stable-branch documentation source SGML files, do: - - make dok dok-pdf # (or 'make redhat-dok dok-pdf' if 'make dok' doesn't work for you) + make dok - That will generate doc/webserver/user-manual, doc/webserver/developer-manual, doc/webserver/faq, - doc/pdf/*.pdf and doc/webserver/index.html automatically. @@ -2950,7 +2929,7 @@ at sourceforge. Three simple steps: doc/webserver/man-page/privoxy-man-page.html by running make man. (This is a separate target due to dependencies on some obscure perl scripts - [now in CVS, but not well tested]. See comments in GNUmakefile.) + [now in Git, but not well tested]. See comments in GNUmakefile.) If you want to add new files to the webserver, create them locally in @@ -2958,16 +2937,14 @@ at sourceforge. Three simple steps: create new directories under doc/webserver). - Next, commit any changes from the above steps to CVS. All set? + Next, commit any changes from the above steps to Git. All set? If these are docs in the stable branch, then do: - make webserver - - This will do the upload to the + This will do the upload to the webserver (www.privoxy.org) and ensure all files and directories there are group writable. @@ -2979,46 +2956,6 @@ at sourceforge. Three simple steps: - - Contacting the developers, Bug Reporting and Feature Requests - - &contacting; - - - - - -Privoxy Copyright, License and History - - - ©right; - - - -License - - &license; - - - - - -History - - &history; - - - - - - - See also - - &seealso; - - - -