7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy User Manual"
10 HREF="index.html"><LINK
13 HREF="introduction.html"><LINK
15 TITLE="Quickstart to Using Privoxy"
16 HREF="quickstart.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy User Manual</TH
46 HREF="introduction.html"
59 HREF="quickstart.html"
79 > is available as raw source code (tarball
80 or via CVS), or pre-compiled binaries for various platforms. See the <A
81 HREF="http://sourceforge.net/projects/ijbswa/"
83 >Privoxy Project Page</A
85 the most up to date release information.
89 > is also available via <A
90 HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/"
94 This is the recommended approach at this time. But
95 please be aware that CVS is constantly changing, and it may break in
101 > is known to run on Win32, Mac
102 OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, and many flavors
103 of Unix. There are source and binary releases for these available for
105 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
107 >http://sourceforge.net/project/showfiles.php?group_id=11118</A
114 NAME="INSTALLATION-SOURCE"
118 > There are several ways to install <SPAN
127 autoconf and GNU make (gmake) are required. Source is available as gzipped
128 tar archives. For this, first unpack the source: </P
138 > tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
139 cd privoxy-2.9.13-beta
146 > For retrieving the current CVS sources, you'll need the CVS
147 package installed first. Note CVS source is development quality,
148 and may not be stable, or well tested. To download CVS source:</P
158 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
159 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
167 > This will create a directory named <TT
171 contain the source tree.</P
173 > Then, in either case, to build from unpacked tarball or CVS source:</P
185 ./configure (--help to see options)
186 make (the make from gnu, gmake for *BSD)
188 make -n install (to see where all the files will go)
189 make install (to really install)
196 > Redhat and SuSE src and binary RPMs can be built with
210 > from unpacked sources. You
211 will need to run <SPAN
215 >autoconf; autoheader;
218 > beforehand. *BSD will require gmake (from
220 HREF="http://www.gnu.org"
222 >http://www.gnu.org</A
226 > For Redhat and SuSE Linux RPM packages, see below.</P
232 NAME="INSTALLATION-RH"
236 > To build Redhat RPM packages from source, install source as above. Then:</P
256 > This will create both binary and src RPMs in the usual places. Example:</P
258 > /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm</P
260 > /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm</P
262 > To install, of course:</P
272 > rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
279 > This will place the <SPAN
289 >/var/log/privoxy/</TT
293 >ckconfig privoxy on</B
298 > start automatically during init. </P
305 NAME="INSTALLATION-SUSE"
309 > To build SuSE RPM packages, install source as above. Then:</P
329 > This will create both binary and src RPMs in the usual places. Example:</P
331 > /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm</P
333 > /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm</P
335 > To install, of course:</P
345 > rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
352 > This will place the <SPAN
362 >/var/log/privoxy/</TT
370 NAME="INSTALLATION-OS2"
377 > is packaged in a WarpIN self-
378 installing archive. The self-installing program will be named depending
379 on the release version, something like:
382 >privoxyos2_setup_2.9.13.exe</TT
383 >. In order to install it, simply
384 run this executable or double-click on its icon and follow the WarpIN
385 installation panels. A shadow of the <SPAN
389 executable will be placed in your startup folder so it will start
390 automatically whenever OS/2 starts.</P
392 > The directory you choose to install <SPAN
396 into will contain all of the configuration files.</P
398 > If you would like to build binary images on OS/2 yourself, you will need
399 a few Unix-like tools: autoconf, autoheader and sh. These tools will be
400 used to create the required config.h file, which is not part of the
401 source distribution because it differs based on platform. You will also
403 The distribution has been created using IBM VisualAge compilers, but you
404 can use any compiler you like. GCC/EMX has the disadvantage of needing
405 to be single-threaded due to a limitation of EMX's implementation of the
411 > In addition to needing the source code distribution as outlined earlier,
412 you will want to extract the <TT
415 > directory from CVS:
424 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
425 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
431 This will create a directory named os2setup/, which will contain the
439 which is used to completely create the binary distribution. The sequence
440 of events for building the executable for yourself goes something like this:
454 nmake -f Makefile.vac
460 You will see this sequence laid out in <TT
470 NAME="INSTALLATION-WIN"
474 >Click-click. (I need help on this. Not a clue here. Also for
475 configuration section below. HB.)</P
482 NAME="INSTALLATION-OTHER"
486 > Some quick notes on other Operating Systems.</P
488 > For FreeBSD (and other *BSDs?), the build will require <B
492 instead of the included <B
500 HREF="http://www.gnu.org"
502 >http://www.gnu.org</A
504 The rest should be the same as above for Linux/Unix.</P
523 HREF="introduction.html"
539 HREF="quickstart.html"
558 >Quickstart to Using <SPAN