Installation

2.1.1. Red Hat and Fedora RPMs2.1.1. Red Hat and Fedora RPMs

RPMs can be installed with rpm -Uvh privoxy-3.0.6-1.rpmrpm -Uvh privoxy-3.0.11-1.rpm, and will use If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-3.0.6-1.src.rpmrpm --rebuild privoxy-3.0.11-1.src.rpm. This will use your locally installed libraries and RPM version.

2.1.2. Debian2.1.2. Debian and Ubuntu

DEBs can be installed with 2.1.3. Windows2.1.3. Windows

Just double-click the installer, which will guide you through the installation process. You will find the configuration files @@ -210,7 +213,7 @@ CLASS="APPLICATION" >Privoxy in.

Version 3.0.4 introduced full Version 3.0.5 beta introduced full Windows service @@ -306,8 +309,8 @@ CLASS="SECT3" CLASS="SECT3" >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX2.1.4. Solaris

Create a new directory, 2.1.5. OS/22.1.5. OS/2

First, make sure that no previous installations of 2.1.6. Mac OSX2.1.6. Mac OS X

Unzip the downloaded file (you can either double-click on the file - from the finder, or from the desktop if you downloaded it there). - Then, double-click on the package installer icon named - Privoxy.pkg - and follow the installation process. - Privoxy will be installed in the folder - /Library/Privoxy. - It will start automatically whenever you start up. To prevent it from - starting automatically, remove or rename the folder +> Unzip the downloaded file (you can either double-click on the zip file + icon from the Finder, or from the desktop if you downloaded it there). + Then, double-click on the package installer icon and follow the + installation process.

The privoxy service will automatically start after a successful + installation (in addition to every time your computer starts up). To + prevent the privoxy service from automatically starting when your + computer starts up, remove or rename the folder named /Library/StartupItems/Privoxy.

To start Privoxy by hand, double-click on - StartPrivoxy.command in the - /Library/Privoxy folder. - Or, type this command in the Terminal:

/Library/Privoxy/StartPrivoxy.command -

You will be prompted for the administrator password.

To manually start or stop the privoxy service, use the Privoxy Utility + for Mac OS X. This application controls the privoxy service (e.g. + starting and stopping the service as well as uninstalling the software).

2.1.7. AmigaOS2.1.7. AmigaOS Copy and then unpack the 2.1.8. FreeBSD Privoxy is part of FreeBSD's Ports Collection, you can build and install + it with cd /usr/ports/www/privoxy; make install clean. If you don't use the ports, you can fetch and install + the package with pkg_add -r privoxy. The port skeleton and the package can also be downloaded from the + File Release + Page, but there's no reason to use them unless you're interested in the + beta releases which are only available there.

`2.1.8. Gentoo`

2.1.9. Gentoo Gentoo source packages (Ebuilds) for under Gentoo just do first emerge rsyncemerge --sync to get the latest changes from the Portage tree. With , the documentation is in /usr/share/doc/privoxy-3.0.6/usr/share/doc/privoxy-3.0.11 and the Log directory is in 2.2. Building from Source2.2. Building from Source The most convenient way to obtain the sources is to download the source tarball from our project download page tar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz] - cd privoxy-3.0.6 tar xzvf privoxy-3.0.11-stable-src.tar.gz + cd privoxy-3.0.11-stable Then build as above.Then build as above. In Privoxy 3.0.7 and later, all of these options +can also be disabled through the configuration file. "new" extension. default.action, default.filter, and - standard.action extension. default.action and default.filter + will be overwritten. You will then need - to manually update the other installed configuration files as needed. All - template files will be overwritten. If you have customized, local templates, - you should save these first, and in fact it is wise to always save any + to manually update the other installed configuration files as needed. The + default template files will be overwritten. If you have + customized, local templates, these should be stored safely in a separate + directory and defined in config by the + "templdir" directive. It is of course wise to always back-up any important configuration files "just in case"2.3. Keeping your Installation Up-to-Date2.3. Keeping your Installation Up-to-Date As user feedback comes in and development continues, we will make updated versions of both the main actions file (as a separate package