See the note to upgraders section below.
How to install the binary packages depends on your operating system:
RPMs can be installed with rpm -Uvh privoxy-3.1.1-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.1.1-1.src.rpmrpm --rebuild privoxy-3.0.4-1.src.rpm. This will use your locally installed libraries and RPM version.
DEBs can be installed with dpkg -i - privoxy_3.1.1-1.deb, and will use - apt-get install privoxy, + and will use /etc/privoxy for the location of configuration - files.
for the location of + configuration files.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.
Create a new directory, 2.1.5. OS/2
2.1.5. OS/2
First, make sure that no previous installations of
Unzip the downloaded file (you can either double-click on the file
from the finder, or from the desktop if you downloaded it there).
@@ -324,7 +338,9 @@ CLASS="SECT3"
> Copy and then unpack the Gentoo source packages (Ebuilds) for , the
documentation is in /usr/share/doc/privoxy-3.1.1/usr/share/doc/privoxy-3.0.4
and the Log directory is in 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: 2.1.6. Mac OSX
2.1.6. Mac OSX2.1.7. AmigaOS
2.1.7. AmigaOS2.1.8. Gentoo
2.1.8. Gentoo2.2. Building from Source
2.2. Building from Source
tar xzvf privoxy-3.1.1-beta-src* [.tgz or .tar.gz] - cd privoxy-3.1.1-betatar 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.
autoheader - autoconf - ./configure # (--help to see options) - make # (the make from gnu, gmake for *BSD) - su - make -n install # (to see where all the files will go) - make install # (to really install)privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell |
Warningprivoxy:*:7777: |
Some binary packages may do this for you.
Then, to build from either unpacked tarball or CVS source:
- The "make install" target is temporary quite broken! It is - recommended to use a binary package, or do a source build, and manually - install the components. Sorry. - autoheader + autoconf + ./configure # (--help to see options) + make # (the make from GNU, sometimes called gmake) + su + make -n install # (to see where all the files will go) + make -s install # (to really install, -s to silence output) |
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-Date
2.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 +> In order not to lose your personal changes and adjustments when updating to the latest default.actionNextNote to UpgradersWhat's New in this Release