7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Note to Upgraders"
17 HREF="upgradersnote.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy User Manual</TH
48 HREF="introduction.html"
62 HREF="upgradersnote.html"
76 NAME="INSTALLATION">2. Installation</H1
81 > is available both in convenient pre-compiled
82 packages for a wide range of operating systems, and as raw source code.
83 For most users, we recommend using the packages, which can be downloaded from our
85 HREF="http://sourceforge.net/projects/ijbswa/"
91 > Note: If you have a previous <SPAN
98 > installation on your system, you
99 will need to remove it. On some platforms, this may be done for you as part
100 of their installation procedure. (See below for your platform). In any case
105 >be sure to backup your old configuration if it is valuable to
109 HREF="upgradersnote.html"
118 NAME="INSTALLATION-PACKAGES">2.1. Binary Packages</H2
120 >How to install the binary packages depends on your operating system:</P
126 NAME="INSTALLATION-PACK-RPM">2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
128 > RPMs can be installed with <TT
130 >rpm -Uvh privoxy-2.9.15-1.rpm</TT
136 of configuration files.</P
138 > Note that on Red Hat, <SPAN
148 > be automatically started on system boot. You will
149 need to enable that using <B
156 >, or similar methods. Note that SuSE will
157 automatically start Privoxy in the boot process.</P
159 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
162 >rpm --rebuild privoxy-2.9.15-1.src.rpm</TT
164 will use your locally installed libraries and RPM version. </P
166 > Also note that if you have a <SPAN
170 on your system, you need to remove it first, because the packages conflict.
171 Otherwise, RPM will try to remove <SPAN
175 automatically, before installing <SPAN
185 NAME="INSTALLATION-DEB">2.1.2. Debian</H3
187 > DEBs can be installed with <TT
190 privoxy_2.9.15-1.deb</TT
195 > for the location of configuration
203 NAME="INSTALLATION-PACK-WIN">2.1.3. Windows</H3
205 > Just double-click the installer, which will guide you through
206 the installation process. You will find the configuration files
207 in the same directory as you installed Privoxy in. We do not
208 use the registry of Windows. </P
215 NAME="INSTALLATION-PACK-BINTGZ">2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
217 > Create a new directory, <TT
220 > to it, then unzip and
221 untar the archive. For the most part, you'll have to figure out where
229 NAME="INSTALLATION-OS2">2.1.5. OS/2</H3
231 > First, make sure that no previous installations of
240 system. Check that no <SPAN
248 your startup folder. </P
250 > Then, just double-click the WarpIN self-installing archive, which will
251 guide you through the installation process. A shadow of the
255 > executable will be placed in your
256 startup folder so it will start automatically whenever OS/2 starts.</P
258 > The directory you choose to install <SPAN
262 into will contain all of the configuration files.</P
269 NAME="INSTALLATION-MAC">2.1.6. Max OSX</H3
271 > Unzip the downloaded package (you can either double-click on the file
272 in the finder, or on the desktop if you downloaded it there). Then,
273 double-click on the package installer icon and follow the installation
278 > will be installed in the subdirectory
281 >/Applications/Privoxy.app</TT
286 > will set itself up to start
287 automatically on system bring-up via
290 >/System/Library/StartupItems/Privoxy</TT
298 NAME="INSTALLATION-AMIGA">2.1.7. AmigaOS</H3
300 > Copy and then unpack the <TT
303 > archive to a suitable location.
304 All necessary files will be installed into <SPAN
308 directory, including all configuration and log files. To uninstall, just
309 remove this directory.</P
317 NAME="INSTALLATION-SOURCE">2.2. Building from Source</H2
319 > The most convenient way to obtain the <SPAN
323 is to download the source tarball from our <A
324 HREF="http://sf.net/projects/ijbswa/"
330 > If you like to live on the bleeding edge and are not afraid of using
331 possibly unstable development versions, you can check out the up-to-the-minute
332 version directly from <A
333 HREF="http://sourceforge.net/cvs/?group_id=11118"
337 > or simply download <A
338 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
349 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
354 HREF="http://www.gnu.org/software/make/make.html"
358 >, and, of course, a C compiler like <A
359 HREF="http://www.gnu.org/software/gcc/gcc.html"
364 > When building from a source tarball (either release version or
366 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
370 >), first unpack the source: </P
380 > tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
381 cd privoxy-2.9.15-beta</PRE
387 > For retrieving the current CVS sources, you'll need CVS installed.
388 Note that sources from CVS are development quality, and may not be
389 stable, or well tested. To download CVS source:</P
399 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
400 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
407 > This will create a directory named <TT
411 contain the source tree.</P
413 > Then, in either case, to build from unpacked tarball or CVS source:</P
425 ./configure # (--help to see options)
426 make # (the make from gnu, gmake for *BSD)
428 make -n install # (to see where all the files will go)
429 make install # (to really install)</PRE
435 > If you have gnu make, you can have the first four steps
436 automatically done for you by just typing:</P
452 > in the freshly downloaded or unpacked source directory.</P
454 > For more detailed instructions on how to build Redhat and SuSE RPMs,
455 Windows self-extracting installers, building on platforms with
456 special requirements etc, please consult the <A
457 HREF="../developer-manual/newrelease.html"
468 SUMMARY="Footer navigation table"
479 HREF="introduction.html"
497 HREF="upgradersnote.html"
517 >Note to Upgraders</TD