* USA
*
*********************************************************************/
-
-------------------------------------------------------------------------------
When building from a source tarball, first unpack the source:
- tar xzvf privoxy-3.0.25-beta-src.tar.gz
- cd privoxy-3.0.25-beta
+ tar xzvf privoxy-3.0.33-stable-src.tar.gz
+ cd privoxy-3.0.33-stable
-For retrieving the current CVS sources, you'll need a CVS client installed.
-Note that sources from CVS are typically development quality, and may not be
-stable, or well tested. To download CVS source, check the Sourceforge
-documentation, which might give commands like:
+To build the development version, you can get the source code by doing:
- 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
+ cd <root-dir>
+ git clone https://www.privoxy.org/git/privoxy.git
-This will create a directory named current/, which will contain the source
-tree.
+This will create a directory named <root-dir>/privoxy/, which will contain the
+source tree.
-You can also check out any Privoxy "branch", just exchange the current name
-with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs tree).
+Note that source code in Git is development quality, and may not be stable or
+well tested.
-It is also strongly recommended to not run Privoxy as root. You should
-configure/install/run Privoxy as an unprivileged user, preferably by creating a
-"privoxy" user 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).
+It is strongly recommended to not run Privoxy as root. You should configure/
+install/run Privoxy as an unprivileged user, preferably by creating a "privoxy"
+user 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).
/etc/passwd might then look like:
Some binary packages may do this for you.
-Then, to build from either unpacked tarball or CVS source:
+Then, to build from either unpacked tarball or Git checkout:
- autoheader
- autoconf
- ./configure # (--help to see options)
- 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)
+ autoheader
+ autoconf
+ ./configure # (--help to see options)
+ 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)
Using GNU make, you can have the first four steps automatically done for you by
just typing:
easily bypass the proxy (e.g. "Go There Anyway"), or alter their own
configurations, configure like this:
- ./configure --disable-toggle --disable-editor --disable-force
+ ./configure --disable-toggle --disable-editor --disable-force
Note that all of these options can also be disabled through the configuration
file.
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
+ 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