X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Finstallation.html;h=192498feb43607ae617560bde19800cabba6682d;hp=3defd45c5becfe83d87951c6e2505f87abdfe08e;hb=56d03106907472899fa6e8933e81058744ce0fed;hpb=0fe95c6387d3cd7173ad01a09acd06c111b189fe diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index 3defd45c..192498fe 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -77,240 +77,289 @@ NAME="INSTALLATION" > Privoxy is available as raw source code (tarball - or via CVS), or pre-compiled binaries for various platforms. See the is available both in convenient pre-compiled + packages for a wide range of operating systems, and as raw source code. + For most users, we recommend using the packages, which can be downloaded from our + Privoxy Project Page for - the most up to date release information. - Privoxy is also available via .

If you like to live on the bleeding edge and are not afraid of using + possibly unstable development versions, you can check out the up-to-the-minute + version directly from CVS. - This is the recommended approach at this time. But - please be aware that CVS is constantly changing, and it may break in - mysterious ways.

the + CVS repository or simply download the nightly CVS + tarball.

At present, Privoxy is known to run on Win32, Mac - OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, and many flavors - of Unix. There are source and binary releases for these available for - download at http://sourceforge.net/project/showfiles.php?group_id=11118.

3.1. Source3.1. Binary Packages

There are several ways to install Note: If you have a previous Privoxy.

To build Junkbuster or + Privoxy from source, - autoconf and GNU make (gmake) are required. Source is available as gzipped - tar archives. For this, first unpack the source: 

 tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.13-beta
-

For retrieving the current CVS sources, you'll need the CVS - package installed first. Note CVS source is development quality, - and may not be stable, or well tested. To download CVS source:

installation on your system, you + will need to remove it. Some platforms do this for you as part + of their installation procedure. (See below for your platform).

In any case be sure to backup your old configuration + if it is valuable to you. See the + note to upgraders.

  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
-  cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
-  cd current
-

How to install the binary packages depends on your operating system:

3.1.1. Red Hat and SuSE RPMs

This will create a directory named RPMs can be installed with rpm -Uvh privoxy-2.9.14-1.rpm, + and will use current/, which will - contain the source tree.

Then, in either case, to build from unpacked tarball or CVS source:

 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)
-

/etc/privoxy for the location + of configuration files.

Redhat and SuSE src and binary RPMs can be built with - "make redhat-dist" or - " Note that on Red Hat, Privoxy will not be + automatically started on system boot. You will need to enable that using + make suse-dist" from unpacked sources. You - will need to run "chkconfig, autoconf; autoheader; - ./configure" beforehand. *BSD will require gmake (from - http://www.gnu.org). -

ntsysv, or similar method.

If you have problems with failed dependencies, try rebuilding the SRC RPM: + rpm --rebuild privoxy-2.9.14-1.src.rpm;. This + will use your locally installed libraries and RPM version.

For Redhat and SuSE Linux RPM packages, see below.

Also note that if you have a Junkbuster RPM installed + on your system, you need to remove it first, because the packages conflict. + Otherwise, RPM will try to remove Junkbuster + automatically, before installing Privoxy.

3.1.1. Red Hat3.1.2. Debian

To build Redhat RPM packages from source, install source as above. Then:

 autoheader
- autoconf
- ./configure
- make redhat-dist
-

FIXME.

3.1.3. Windows

This will create both binary and src RPMs in the usual places. Example:

Just double-click the installer, which will guide you through + the installation process.

3.1.4. Solaris, NetBSD, FreeBSD, HP-UX

   /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm

Create a new directory, cd to it, then unzip and + untar the archive. For the most part, you'll have to figure out where + things go. FIXME.

3.1.5. OS/2

   /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm

First, make sure that no previous installations of + Junkbuster and / or + Privoxy are left on your + system. You can do this by

To install, of course:

Then, just double-click the WarpIN self-installing archive, which will + guide you through the installation process. A shadow of the + Privoxy executable will be placed in your + startup folder so it will start automatically whenever OS/2 starts.

 rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
-

The directory you choose to install Privoxy + into will contain all of the configuration files.

3.1.6. Max OSX

This will place the Unzip the downloaded package (you can either double-click on the file + in the finder, or on the desktop if you downloaded it there). Then, + double-click on the package installer icon and follow the installation + process. + Privoxy configuration - files in /etc/privoxy/, and log files in +> will be installed in the subdirectory /var/log/privoxy/. Run - "chkconfig privoxy on" to have +CLASS="LITERAL" +>/Applications/Privoxy.app. Privoxy start automatically during init.

will set itself up to start + automatically on system bringup via + /System/Library/StartupItems/Privoxy.

3.1.2. SuSE3.1.7. AmigaOS

To build SuSE RPM packages, install source as above. Then:

Copy and then unpack the lha archive to a suitable location. + All necessary files will be installed into Privoxy + directory, including all configuration and log files. To uninstall, just + remove this directory.

Start Privoxy (with RUN <>NIL:) in your + startnet script (AmiTCP), in + s:user-startup (RoadShow), as startup program in your + startup script (Genesis), or as startup action (Miami and MiamiDx). + Privoxy will automatically quit when you quit your + TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that + Privoxy is still running).

3.2. Building from Source

To build Privoxy from source, + autoheader, autoconf, GNU make + (gmake), and, of course, a C compiler are required.

When building from a source tarball (either release version or + nightly CVS tarball), first unpack the source: 

 autoheader
- autoconf
- ./configure
- make suse-dist
+> tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.14-beta

This will create both binary and src RPMs in the usual places. Example:

   /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm

   /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm

To install, of course:

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:

 rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
+>  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
+  cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
+  cd current

This will place the Privoxy configuration - files in /etc/privoxy/, and log files in - /var/log/privoxy/.

3.1.3. OS/2

Privoxy is packaged in a WarpIN self- - installing archive. The self-installing program will be named depending - on the release version, something like: - This will create a directory named privoxyos2_setup_2.9.13.exe. In order to install it, simply - run this executable or double-click on its icon and follow the WarpIN - installation panels. A shadow of the Privoxy - executable will be placed in your startup folder so it will start - automatically whenever OS/2 starts.

The directory you choose to install Privoxy - into will contain all of the configuration files.

current/, which will + contain the source tree.

If you would like to build binary images on OS/2 yourself, you will need - a few Unix-like tools: autoconf, autoheader and sh. These tools will be - used to create the required config.h file, which is not part of the - source distribution because it differs based on platform. You will also - need a compiler. - The distribution has been created using IBM VisualAge compilers, but you - can use any compiler you like. GCC/EMX has the disadvantage of needing - to be single-threaded due to a limitation of EMX's implementation of the - select() socket call.

Then, in either case, to build from unpacked tarball or CVS source:

In addition to needing the source code distribution as outlined earlier, - you will want to extract the os2seutp directory from CVS: - 
 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login          
- cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
+> 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)
- This will create a directory named os2setup/, which will contain the - Makefile.vac makefile and os2build.cmd - which is used to completely create the binary distribution. The sequence - of events for building the executable for yourself goes something like this: -

If you have gnu make, you can have the first four steps + automatically done for you by just typing

 cd current
- autoheader
- autoconf
- sh configure
- cd ..\os2setup
- nmake -f Makefile.vac
+>  make
- You will see this sequence laid out in os2build.cmd.

3.1.4. Windows

Click-click. (I need help on this. Not a clue here. Also for -configuration section below. HB.)

3.1.5. Other

Some quick notes on other Operating Systems.

in the freshly downloaded or unpacked source directory.

For FreeBSD (and other *BSDs?), the build will require gmake - instead of the included make. gmake is - available from 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 http://www.gnu.org. - The rest should be the same as above for Linux/Unix.

developer manual.