X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Finstallation.html;h=283ec9a6beaadfda9553ffc2b9e10caa3000eb82;hb=086d4aacf2fe1d729b4f4a67a7167cb6f19db043;hp=56700d0f611956de2a120583ec145589de58805b;hpb=16e9ef297b4cf15a61876abcc794e5a058500e4b;p=privoxy.git diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index 56700d0f..283ec9a6 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -1,567 +1,437 @@ -
Privoxy is available as raw source code (tarball - or via CVS), or pre-compiled binaries for various platforms. See the Privoxy Project Page for - the most up to date release information. - Privoxy is also available via 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.
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.
There are several ways to install Privoxy.
To build 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:
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 create a directory named current/, which will - contain the source tree.
Then, in either case, to build from unpacked tarball or CVS source:
autoheader + + + ++ |
+
Using GNU make, you can have the first four steps automatically done for you by just + typing:
+
+ make+ |
+
in the freshly downloaded or unpacked source directory.
+To build an executable with security enhanced features so that users cannot easily bypass the proxy (e.g. + "Go There Anyway"), or alter their own configurations, configure like this:
+
+ ./configure --disable-toggle --disable-editor --disable-force+ |
+
Note that all of these options can also be disabled through the configuration file.
+WARNING: If installing as root, the install will fail + unless a non-root user or group is specified, or a privoxy user and group already exist + on the system. If a non-root user is specified, and no group, then the installation will try to also use a group + of the same name as "user". If a group is specified (and no user), then the support + files will be installed as writable by that group, and owned by the user running the installation.
+configure accepts --with-user and --with-group options for setting user and group ownership of the configuration files (which need + to be writable by the daemon). The specified user must already + exist. When starting Privoxy, it must be run as this same user to + insure write access to configuration and log files!
+Alternately, you can specify user and group on the make command line, but be sure both already exist:
+
+ 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 an install to anywhere besides /usr/local, be sure to set the appropriate paths + with the correct configure options (./configure --help). Non-privileged users must of + course have write access permissions to wherever the target installation is going.
+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 documentation 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 should 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 local configuration files, most of these will not be overwritten, and + the new ones will be installed with a "new" extension. default.action and + default.filter will be overwritten. You will then need 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". 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 RPMs, Windows self-extracting installers, building on + platforms with special requirements etc, please consult the developer manual.
+Install the Cygwin utilities needed to build Privoxy. If you have a 64 + bit CPU (which most people do by now), get the Cygwin setup-x86_64.exe program here (the .sig file is here).
+Run the setup program and from View / Category select:
+
+ Devel + autoconf 2.5 + automake 1.15 + binutils + cmake + gcc-core + gcc-g++ + git + make + mingw64-i686-gcc-core + mingw64-i686-zlib + Editors + vim + Libs + libxslt: GNOME XSLT library (runtime) + Net + curl + openssh + Text + docbook-dssl + docbook-sgml31 + docbook-utils + openjade + Utils + gnupg + Web + w3m+ |
+
If you haven't already downloaded the Privoxy source code, get it now:
+
+ mkdir <root-dir> + cd <root-dir> + git clone https://www.privoxy.org/git/privoxy.git+ |
+
Get the source code (.zip or .tar.gz) for tidy from https://github.com/htacg/tidy-html5/releases, unzip into <root-dir> and build the + software:
+
+ cd <root-dir> + cd tidy-html5-x.y.z/build/cmake + cmake ../.. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIB:BOOL=OFF -DCMAKE_INSTALL_PREFIX=/usr/local + make && make install+ |
+
If you want to be able to make a Windows release package, get the NSIS .zip file from https://sourceforge.net/projects/nsis/files/NSIS%203/ and extract the NSIS directory to privoxy/windows. Then edit the windows/GNUmakefile to set the location of the NSIS executable + - eg:
+
+ # Path to NSIS +MAKENSIS = ./nsis/makensis.exe+ |
+
To build just the Privoxy executable and not the whole installation package, do:
+
+ cd <root-dir>/privoxy + ./windows/MYconfigure && make+ |
+
Privoxy uses the GNU Autotools + for building software, so the process is:
+
+ $ autoheader # creates config.h.in + $ autoconf # uses config.h.in to create the configure shell script + $ ./configure [options] # creates GNUmakefile + $ make [options] # builds the program+ |
+
The usual configure options for building a native Windows application under + cygwin are
+
+ --host=i686-w64-mingw32 + --enable-mingw32 + --enable-zlib + --enable-static-linking + --disable-pthread + --disable-dynamic-pcre+ |
+
You can set the CFLAGS and LDFLAGS envars before running + configure to set compiler and linker flags. For example:
+
+ $ export CFLAGS="-O2" # set gcc optimization level + $ export LDFLAGS="-Wl,--nxcompat" # Enable DEP + $ ./configure --host=i686-w64-mingw32 --enable-mingw32 --enable-zlib \ + > --enable-static-linking --disable-pthread --disable-dynamic-pcre + $ make # build Privoxy+ |
+
See the Developer's + Manual for building a Windows release package.
+If you wish to receive an email notification whenever we release updates of Privoxy or the actions file, subscribe to our announce mailing + list, privoxy-announce@lists.privoxy.org.
+In order not to lose your personal changes and adjustments when updating to the latest default.action file we strongly recommend + that you use user.action and user.filter for your local + customizations of Privoxy. See the Chapter on + actions files for details.
+