7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Quickstart to Using Privoxy"
17 HREF="quickstart.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="introduction.html"
60 HREF="quickstart.html"
80 > is available as raw source code (tarball
81 or via CVS), or pre-compiled binaries for various platforms. See the <A
82 HREF="http://sourceforge.net/projects/ijbswa/"
84 >Privoxy Project Page</A
86 the most up to date release information.
90 > is also available via <A
91 HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/"
95 This is the recommended approach at this time. But
96 please be aware that CVS is constantly changing, and it may break in
102 > is known to run on Win32, Mac
103 OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, and many flavors
104 of Unix. There are source and binary releases for these available for
106 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
108 >http://sourceforge.net/project/showfiles.php?group_id=11118</A
115 NAME="INSTALLATION-SOURCE"
119 > There are several ways to install <SPAN
128 autoconf and GNU make (gmake) are required. Source is available as gzipped
129 tar archives. For this, first unpack the source: </P
139 > tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
140 cd privoxy-2.9.14-beta
147 > For retrieving the current CVS sources, you'll need the CVS
148 package installed first. Note CVS source is development quality,
149 and may not be stable, or well tested. To download CVS source:</P
159 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
160 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
168 > This will create a directory named <TT
172 contain the source tree.</P
174 > Then, in either case, to build from unpacked tarball or CVS source:</P
186 ./configure (--help to see options)
187 make (the make from gnu, gmake for *BSD)
189 make -n install (to see where all the files will go)
190 make install (to really install)
197 > Redhat and SuSE src and binary RPMs can be built with
211 > from unpacked sources. You
212 will need to run <SPAN
216 >autoconf; autoheader;
219 > beforehand. *BSD will require gmake (from
221 HREF="http://www.gnu.org"
223 >http://www.gnu.org</A
227 > For Redhat and SuSE Linux RPM packages, see below.</P
233 NAME="INSTALLATION-RH"
237 > To build Redhat RPM packages from source, install source as above. Then:</P
257 > This will create both binary and src RPMs in the usual places. Example:</P
259 > /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm</P
261 > /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm</P
263 > To install, of course:</P
273 > rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
280 > This will place the <SPAN
290 >/var/log/privoxy/</TT
294 >ckconfig privoxy on</B
299 > start automatically during init. </P
306 NAME="INSTALLATION-SUSE"
310 > To build SuSE RPM packages, install source as above. Then:</P
330 > This will create both binary and src RPMs in the usual places. Example:</P
332 > /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm</P
334 > /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm</P
336 > To install, of course:</P
346 > rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
353 > This will place the <SPAN
363 >/var/log/privoxy/</TT
371 NAME="INSTALLATION-OS2"
378 > is packaged in a WarpIN self-
379 installing archive. The self-installing program will be named depending
380 on the release version, something like:
383 >privoxyos2_setup_2.9.14.exe</TT
384 >. In order to install it, simply
385 run this executable or double-click on its icon and follow the WarpIN
386 installation panels. A shadow of the <SPAN
390 executable will be placed in your startup folder so it will start
391 automatically whenever OS/2 starts.</P
393 > The directory you choose to install <SPAN
397 into will contain all of the configuration files.</P
399 > If you would like to build binary images on OS/2 yourself, you will need
400 a few Unix-like tools: autoconf, autoheader and sh. These tools will be
401 used to create the required config.h file, which is not part of the
402 source distribution because it differs based on platform. You will also
404 The distribution has been created using IBM VisualAge compilers, but you
405 can use any compiler you like. GCC/EMX has the disadvantage of needing
406 to be single-threaded due to a limitation of EMX's implementation of the
412 > In addition to needing the source code distribution as outlined earlier,
413 you will want to extract the <TT
416 > directory from CVS:
425 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
426 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
432 This will create a directory named os2setup/, which will contain the
440 which is used to completely create the binary distribution. The sequence
441 of events for building the executable for yourself goes something like this:
455 nmake -f Makefile.vac
461 You will see this sequence laid out in <TT
471 NAME="INSTALLATION-WIN"
475 >Click-click. (I need help on this. Not a clue here. Also for
476 configuration section below. HB.)</P
483 NAME="INSTALLATION-OTHER"
487 > Some quick notes on other Operating Systems.</P
489 > For FreeBSD (and other *BSDs?), the build will require <B
493 instead of the included <B
501 HREF="http://www.gnu.org"
503 >http://www.gnu.org</A
505 The rest should be the same as above for Linux/Unix.</P
524 HREF="introduction.html"
540 HREF="quickstart.html"
559 >Quickstart to Using <SPAN