X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fbuildsource.sgml;h=afc2c6b9582fd88e76d1e06ad5046ad1f2828cbf;hb=3fb5b49e4b9b2e99b1a12205f54ab0e22e77eade;hp=e128d04dae1f082dbc648ea1052d67ccf4ba779b;hpb=d09495686ceb54f830dfecefcdfdde1061cc8f33;p=privoxy.git diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml index e128d04d..afc2c6b9 100644 --- a/doc/source/buildsource.sgml +++ b/doc/source/buildsource.sgml @@ -2,27 +2,27 @@ File : $Source: /cvsroot/ijbswa/current/doc/source/buildsource.sgml,v $ Purpose : Entity included in other project documents. - - $Id: buildsource.sgml,v 2.11 2006/10/14 23:06:48 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org + $Id: buildsource.sgml,v 2.18 2009/02/23 09:03:12 fabiankeil Exp $ + + Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/ See LICENSE. ====================================================================== This file used for inclusion with other documents only. ====================================================================== - If you make changes to this file, please verify the finished + If you make changes to this file, please verify the finished docs all display as intended. This file is included into: user-manual - README + INSTALL --> - To build Privoxy from source, + To build Privoxy from source, autoconf, GNU make @@ -32,18 +32,18 @@ When building from a source tarball, - first unpack the source: + tarball), +--> first unpack the source: - tar xzvf privoxy-&p-version;-src* [.tgz or .tar.gz] - cd privoxy-&p-version; + tar xzvf privoxy-&p-version;-src.tar.gz + cd privoxy-&p-version; @@ -63,7 +63,7 @@ - This will create a directory named current/, which will + This will create a directory named current/, which will contain the source tree. @@ -81,7 +81,7 @@ and group just for this purpose. See your local documentation for the correct command line to do add new users and groups (something like adduser, but the command syntax may vary from platform - to platform). + to platform). @@ -113,7 +113,7 @@ autoheader autoconf ./configure # (--help to see options) - make # (the make from GNU, sometimes called gmake) + make # (the make from GNU, sometimes called gmake) su # Possibly required make -n install # (to see where all the files will go) make -s install # (to really install, -s to silence output) @@ -135,16 +135,17 @@ - To build an executable with security enhanced features so that + 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 - + -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. WARNING: If installing as root, the install will fail @@ -176,9 +177,9 @@ Then build as above. - 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 + 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 @@ -208,15 +209,15 @@ Then build as above. 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. + will be created in /var/run/privoxy.pid. - make install will attempt to set the correct values - in config (main configuration file). You should + 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 + 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. @@ -224,11 +225,13 @@ Then build as above. 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, default.filter, and - standard.action 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 + 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. @@ -238,16 +241,16 @@ Then build as above. 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. + url="http://www.privoxy.org/developer-manual/newrelease.html">developer manual. - The simplest command line to start Privoxy is - $path/privoxy --user=privoxy $path/etc/privoxy/config. - See privoxy --usage, or the man page, for other options, + The simplest command line to start Privoxy is + $path/privoxy --user=privoxy $path/etc/privoxy/config. + See privoxy --usage, or the man page, for other options, and configuration. ]]>