.
Note: If you have a previous Junkbuster or - Privoxy installation on your system, you - will need to remove it. On some platforms, this may be done for you as part - of their installation procedure. (See below for your platform). In any case - Note: + On some platforms, the installer may remove previously installed versions, if + found. (See below for your platform). In any case be sure to backup your old configuration if it is valuable to - you.be sure to backup + your old configuration if it is valuable to you. See the note to - upgradersnote to upgraders section below.
How to install the binary packages depends on your operating system:
RPMs can be installed with RPMs can be installed with rpm -Uvh privoxy-3.0.3-1.rpmrpm -Uvh privoxy-3.0.4-1.rpm, and will use
If you have problems with failed dependencies, try rebuilding the SRC RPM: - rpm --rebuild privoxy-3.0.3-1.src.rpmrpm --rebuild privoxy-3.0.4-1.src.rpm. This will use your locally installed libraries and RPM version.
Junkbuster - automatically, before installing Privoxy.
2.1.2. Debian2.1.2. DebianDEBs can be installed with DEBs can be installed with apt-get install privoxyapt-get install privoxy, and will use 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 - in the same directory as you installed Privoxy in. We do not - use the registry of Windows.
Privoxy in.Version 3.0.4 introduces full Windows service + functionality. On Windows only, the Privoxy + program has two new command line arguments to install and uninstall + Privoxy as a service.
--install[:service_name] +
--uninstall[:service_name] +
After invoking Privoxy with + --install, you will need to bring up the + Windows service console to assign the user you + want Privoxy to run under, and whether or not you + want it to run whenever the system starts. You can start the + Windows services console with the following + command: services.msc If you do not take the manual step + of modifying Privoxy's service settings, it will + not start. Note too that you will need to give Privoxy a user account that + actually exists, or it will not be permitted to + write to its log and configuration files.
Create a new directory, Create a new directory, cdcd to it, then unzip and untar the archive. For the most part, you'll have to figure out where things go.
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 OSX 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.pkgPrivoxy.pkg
and follow the installation process.
Privoxy will be installed in the folder
- /Library/Privoxy/Library/Privoxy.
It will start automatically whenever you start up. To prevent it from
starting automatically, remove or rename the folder
- /Library/StartupItems/Privoxy/Library/StartupItems/Privoxy. To start Privoxy by hand, double-click on
- StartPrivoxy.commandStartPrivoxy.command in the
- /Library/Privoxy/Library/Privoxy folder.
Or, type this command in the Terminal: 2.1.7. AmigaOS2.1.7. AmigaOS Copy and then unpack the 2.1.8. Gentoo2.1.8. Gentoo Gentoo source packages (Ebuilds) for Privoxy under Gentoo just do
- first emerge rsyncemerge rsync to get the latest changes from the
- Portage tree. With emerge privoxyemerge privoxy you install the latest
version. , the
documentation is in /usr/share/doc/privoxy-3.0.3/usr/share/doc/privoxy-3.0.4
and the Log directory is in 2.2. Building from Source2.2. Building from Source The most convenient way to obtain the the
CVS repository or simply download the nightly CVS
- tarball.
To build gcc are required.
When building from a source tarball (either release version or - nightly CVS - tarball), first unpack the source:
When building from a source tarball, + first unpack the source:
tar xzvf privoxy-3.0.3-src* [.tgz or .tar.gz] - cd privoxy-3.0.3tar xzvf privoxy-3.0.4-beta-src* [.tgz or .tar.gz] + cd privoxy-3.0.4-beta |
For retrieving the current CVS sources, you'll need CVS installed. Note that sources from CVS are development quality, and may not be - stable, or well tested. To download CVS source:
cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current +> cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current cd current | , which will
contain the source tree.
privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell |
And then /etc/group, like:
privoxy:*:7777: |
Some binary packages may do this for you.
Then, to build from either unpacked tarball or CVS source:
If you have gnu make, you can have the first four steps +> If you have GNU make, you can have the first four steps automatically done for you by just typing:
make -s install USER=privoxy GROUP=privoxy |
The default installation path for make install is + /usr/local. This may of course be customized with + the various ./configure path options. If you are doing + a root install to anywhere else besides /usr/local, be + sure to set the appropriate paths with the correct configure options + (./configure --help).
If you do install to /usr/local, the install will use + sysconfdir=$prefix/etc/privoxy by default. All other + destinations, and the direct usage of --sysconfdir flag + behave like normal, i.e. will not add the extra privoxy + directory. This is for a safer install, as there may already exist another + program that uses a file with the "config" name, and thus makes + /usr/local/etc cleaner.
If installing to /usr/local, the docs will go by default + to $prefix/share/doc. But if this directory doesn't + exist, it will then try $prefix/doc and install there before + creating a new $prefix/share/doc just for + Privoxy.
Again, if the installs goes to /usr/local, the + localstatedir (ie: var/) will default + to /var instead of $prefix/var so + the logs will go to /var/log/privoxy/, and the pid file + will be created in /var/run/privoxy.pid.
make install will attempt to set the correct values + in config (main configuration file). You may want + to check this to make sure all values are correct. If appropriate, + an init script will be installed, but it is up to the user to determine + how and where to start Privoxy. The init + script should be checked for correct paths and values, if anything other than + a default install is done.
If install finds previous versions of any configuration files, these will not + be overwritten, and the new ones will be installed with a "new" + extension. You will then need to manually update the installed configuration + files as needed. All template files will be overwritten. If you have + customized, local templates, you should save these first. If a previous + version of Privoxy is already running, you will + have to restart it manually.
For more detailed instructions on how to build Redhat and SuSE RPMs, Windows self-extracting installers, building on platforms with special requirements etc, please consult the 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 , ijbswa-announce@lists.sourceforge.net.
In order not to loose your personal changes and adjustments when updating - to the latest In order not to lose your personal changes and adjustments when updating + to the latest default.actiondefault.action file we strongly recommend that you use that you use user.action and + user.action for your - customization of user.filter for your local + customizations of Privoxy. See the NextNote to UpgradersWhat's New in this Release