X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Finstallation.html;h=c73538e570c3a815c7033a69db21e2b8d480953b;hb=72081f829de368392d04076728f8c991178c0080;hp=7c77555be7a8eb970f4b8fd29ed28f5defa8c4ca;hpb=0a3750f6302df8349b5be2e15a9a4fefe3c35889;p=privoxy.git diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index 7c77555b..c73538e5 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -1,13 +1,13 @@ + Installation

3.7. AmigaOS

2.1.7. AmigaOS

Copy and then unpack the directory, including all configuration and log files. To uninstall, just remove this directory.

2.1.8. Gentoo

Start Gentoo source packages (Ebuilds) for Privoxy are + contained in the Gentoo Portage Tree (they are not on the download page, + but there is a Gentoo section, where you can see when a new + Privoxy (with RUN <>NIL:) in your - Version is added to the Portage Tree).

Before installing Privoxy under Gentoo just do + first emerge rsync to get the latest changes from the + Portage tree. With emerge privoxy you install the latest + version.

Configuration files are in startnet script (AmiTCP), in - /etc/privoxy, the + documentation is in s:user-startup (RoadShow), as startup program in your - startup script (Genesis), or as startup action (Miami and MiamiDx). - /usr/share/doc/privoxy-3.0.3 + and the Log directory is in /var/log/privoxy.

2.2. Building from Source

The most convenient way to obtain the Privoxy will automatically quit when you quit your - TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that +> sources + is to download the source tarball from our project + page.

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 the + CVS repository or simply download the nightly CVS + tarball.

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

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

 tar xzvf privoxy-3.0.3-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.3

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

If you have 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.

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 developer manual.

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 actions file (as a separate + package) and the software itself (including the actions file) available for + download.

If you wish to receive an email notification whenever we release updates of Privoxy is still running).

or the actions file, subscribe + to our announce mailing list, ijbswa-announce@lists.sourceforge.net.

In order not to loose your personal changes and adjustments when updating + to the latest default.action file we strongly + recommend that you use user.action for your + customization of Privoxy. See the Chapter on actions files for details.