X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fbuildsource.sgml;h=8e4ee791fb96904b324a9d1649c55b90b90cb297;hb=450621776cfd3ce17d1cbed25897bbba5def7998;hp=d1f4158b5b692a44520bf4ced192d3890da70184;hpb=5e2195df3a7d247074e406e2bf95563973f5c220;p=privoxy.git

diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml
index d1f4158b..8e4ee791 100644
--- a/doc/source/buildsource.sgml
+++ b/doc/source/buildsource.sgml
@@ -3,15 +3,10 @@
 
  Purpose     :  Entity included in other project documents.
                 
- $Id: buildsource.sgml,v 1.3 2002/04/17 13:54:25 oes Exp $
-
- Written by and Copyright (C) 2001 the SourceForge
- Privoxy team. http://www.privoxy.org/
-
- Based on the Internet Junkbuster originally written
- by and Copyright (C) 1997 Anonymous Coders and 
- Junkbusters Corporation.  http://www.junkbusters.com
+ $Id: buildsource.sgml,v 1.8 2002/05/03 17:41:41 oes Exp $
 
+ Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
+ See LICENSE.
 
  ======================================================================
   This file used for inclusion with other documents only.
@@ -29,20 +24,25 @@
 
 <para>
  To build <application>Privoxy</application> from source, 
- autoheader, autoconf,GNU make (gmake), and, of course, a C 
- compiler are required.
+ <ulink url="http://www.gnu.org/software/autoconf/autoconf.html">autoconf</ulink>,
+ <ulink
+ url="http://www.gnu.org/software/make/make.html">GNU make
+ (gmake)</ulink>, and, of course, a C compiler like <ulink
+ url="http://www.gnu.org/software/gcc/gcc.html">gcc</ulink> are required.
 </para>
 
 <para>
  When building from a source tarball (either release version or
- nightly CVS tarball), first unpack the source: 
+ <ulink
+ url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz">nightly CVS
+ tarball</ulink>), first unpack the source: 
 </para>
 
 <para>
  <screen>
  tar xzvf privoxy-&p-version;<![%p-not-stable;[-beta]]>-src* [.tgz or .tar.gz]
  cd privoxy-&p-version;<![%p-not-stable;[-beta]]>
- </screen>
+</screen>
 </para>
 
 <para>
@@ -56,7 +56,7 @@
   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
- </screen>
+</screen>
 </para>
 
 <para>
@@ -77,40 +77,32 @@
  su 
  make -n install  # (to see where all the files will go)
  make install     # (to really install)
- </screen>
+</screen>
 </para>
 
 <para>
   If you have gnu make, you can have the first four steps 
-  automatically done for you by just typing
+  automatically done for you by just typing:
 </para>
 
 <para>
  <screen>
   make
- </screen>
+</screen>
 </para>
 
 <para>
   in the freshly downloaded or unpacked source directory.
 </para>
 
-<para>
- Redhat and SuSE src and binary RPMs can be built with 
- <quote><command>make redhat-dist</command></quote> or
- <quote><command>make suse-dist</command></quote> from unpacked sources. You
- will need to run <quote><command>autoconf; autoheader;
- ./configure</command></quote> beforehand. *BSD will require gmake (from
- <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>). 
- <![%p-readme;[See the user-manual for OS/2 build instructions.]]>
-</para>
-
 <para>
  For more detailed instructions on how to build Redhat and SuSE RPMs,
- Windows self-extracting installers etc, please consult the <ulink
+ Windows self-extracting installers, building on platforms with
+ special requirements etc, please consult the <ulink
  url="../developer-manual/newrelease.html">developer manual</ulink>.
 </para>
 
+<!-- print for README only -->
  <![%p-readme;[
  <para>
   For binary RPM installation, and other platforms, see the user-manual