>Installation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Privoxy User Manual"
HREF="index.html"><LINK
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="NEXT"
-TITLE="Quickstart to Using Privoxy"
-HREF="quickstart.html"><LINK
+TITLE="Note to Upgraders"
+HREF="upgradersnote.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="../p_doc.css"></HEAD
ALIGN="right"
VALIGN="bottom"
><A
-HREF="quickstart.html"
+HREF="upgradersnote.html"
>Next</A
></TD
></TR
CLASS="SECT1"
><A
NAME="INSTALLATION"
->3. Installation</A
+>2. Installation</A
></H1
><P
> <SPAN
<A
HREF="http://sourceforge.net/projects/ijbswa/"
TARGET="_top"
->Privoxy Project Page</A
+>Privoxy Project
+ Page</A
>.</P
><P
-> 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 <A
-HREF="http://sourceforge.net/cvs/?group_id=11118"
-TARGET="_top"
->the
- CVS repository</A
-> or simply download <A
-HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
-TARGET="_top"
->the nightly CVS
- tarball.</A
-></P
-><P
-> At present, <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is known to run on Win32, Mac
- OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, NetBSD, BeOS, and
- many flavors of Unix.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="INSTALLATION-PACKAGES"
->3.1. Binary Packages</A
-></H2
-><P
> Note: If you have a previous <SPAN
CLASS="APPLICATION"
>Junkbuster</SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> 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).</P
-><P
-> In any case <I
+ will need to remove it. On some platforms, this may be done for you as part
+ of their installation procedure. (See below for your platform). In any case
+ <I
CLASS="EMPHASIS"
->be sure to backup your old configuration
- if it is valuable to you.</I
-> See the
- <A
-HREF="quickstart.html#UPGRADERSNOTE"
->note to upgraders</A
->.</P
+>be sure to backup your old configuration if it is valuable to
+ you.</I
+> See the <A
+HREF="upgradersnote.html"
+>note to
+ upgraders</A
+> section below.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="INSTALLATION-PACKAGES"
+>2.1. Binary Packages</A
+></H2
><P
-> How to install the binary packages depends on your operating system:</P
+>How to install the binary packages depends on your operating system:</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="INSTALLATION-PACK-RPM"
->3.1.1. Red Hat and SuSE RPMs</A
+>2.1.1. Red Hat, SuSE RPMs and Conectiva</A
></H3
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-2.9.14-1.rpm</TT
+>rpm -Uvh privoxy-2.9.15-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
> Note that on Red Hat, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> will not be
- automatically started on system boot. You will need to enable that using
- <B
+> will
+ <I
+CLASS="EMPHASIS"
+>not</I
+> be automatically started on system boot. You will
+ need to enable that using <B
CLASS="COMMAND"
>chkconfig</B
->, <B
+>,
+ <B
CLASS="COMMAND"
>ntsysv</B
->, or similar method.</P
+>, or similar methods. Note that SuSE will
+automatically start Privoxy in the boot process.</P
><P
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-2.9.14-1.src.rpm;</TT
+>rpm --rebuild privoxy-2.9.15-1.src.rpm;</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
CLASS="SECT3"
><A
NAME="INSTALLATION-DEB"
->3.1.2. Debian</A
+>2.1.2. Debian</A
></H3
><P
-> FIXME.</P
+> DEBs can be installed with <TT
+CLASS="LITERAL"
+>dpkg -i
+ privoxy_2.9.15-1.deb</TT
+>, and will use
+ <TT
+CLASS="FILENAME"
+>/etc/privoxy</TT
+> for the location of configuration
+ files.</P
></DIV
><DIV
CLASS="SECT3"
CLASS="SECT3"
><A
NAME="INSTALLATION-PACK-WIN"
->3.1.3. Windows</A
+>2.1.3. Windows</A
></H3
><P
> Just double-click the installer, which will guide you through
- the installation process.</P
+ the installation process. You will find the configuration files
+ in the same directory as you installed Privoxy in. We do not
+ use the registry of Windows. </P
></DIV
><DIV
CLASS="SECT3"
CLASS="SECT3"
><A
NAME="INSTALLATION-PACK-BINTGZ"
->3.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
+>2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
></H3
><P
> Create a new directory, <TT
CLASS="SECT3"
><A
NAME="INSTALLATION-OS2"
->3.1.5. OS/2</A
+>2.1.5. OS/2</A
></H3
><P
> First, make sure that no previous installations of
CLASS="SECT3"
><A
NAME="INSTALLATION-MAC"
->3.1.6. Max OSX</A
+>2.1.6. Max OSX</A
></H3
><P
> Unzip the downloaded package (you can either double-click on the file
CLASS="APPLICATION"
>Privoxy</SPAN
> will set itself up to start
- automatically on system bringup via
+ automatically on system bring-up via
<TT
CLASS="LITERAL"
>/System/Library/StartupItems/Privoxy</TT
CLASS="SECT3"
><A
NAME="INSTALLATION-AMIGA"
->3.1.7. AmigaOS</A
+>2.1.7. AmigaOS</A
></H3
><P
> Copy and then unpack the <TT
CLASS="SECT2"
><A
NAME="INSTALLATION-SOURCE"
->3.2. Building from Source</A
+>2.2. Building from Source</A
></H2
><P
+> The most convenient way to obtain the <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> sources
+ is to download the source tarball from our <A
+HREF="http://sf.net/projects/ijbswa/"
+TARGET="_top"
+>project
+ page</A
+>.</P
+><P
+> 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 <A
+HREF="http://sourceforge.net/cvs/?group_id=11118"
+TARGET="_top"
+>the
+ CVS repository</A
+> or simply download <A
+HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
+TARGET="_top"
+>the nightly CVS
+ tarball.</A
+></P
+><P
> To build <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> from source,
- autoheader, autoconf, <A
+ <A
+HREF="http://www.gnu.org/software/autoconf/autoconf.html"
+TARGET="_top"
+>autoconf</A
+>,
+ <A
HREF="http://www.gnu.org/software/make/make.html"
TARGET="_top"
>GNU make
(gmake)</A
->, and, of course, a C compiler are required.</P
+>, and, of course, a C compiler like <A
+HREF="http://www.gnu.org/software/gcc/gcc.html"
+TARGET="_top"
+>gcc</A
+> are required.</P
><P
> When building from a source tarball (either release version or
- nightly CVS tarball), first unpack the source: </P
+ <A
+HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
+TARGET="_top"
+>nightly CVS
+ tarball</A
+>), first unpack the source: </P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
- </PRE
+> tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.15-beta</PRE
></TD
></TR
></TABLE
CLASS="SCREEN"
> 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
- </PRE
+ cd current</PRE
></TD
></TR
></TABLE
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)
- </PRE
+ make install # (to really install)</PRE
></TD
></TR
></TABLE
></P
><P
> If you have gnu make, you can have the first four steps
- automatically done for you by just typing</P
+ automatically done for you by just typing:</P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> make
- </PRE
+> make</PRE
></TD
></TR
></TABLE
ALIGN="right"
VALIGN="top"
><A
-HREF="quickstart.html"
+HREF="upgradersnote.html"
>Next</A
></TD
></TR
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Quickstart to Using <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-></TD
+>Note to Upgraders</TD
></TR
></TABLE
></DIV
projects / privoxy.git / blobdiff