From 048cc96a32f213957bf4ecb844c1f35bfa30cb7c Mon Sep 17 00:00:00 2001 From: hal9 Date: Tue, 25 Mar 2003 00:52:00 +0000 Subject: [PATCH] Add note to not run this branch unless developing. --- README | 58 +++++++--------------------------------------------------- 1 file changed, 7 insertions(+), 51 deletions(-) diff --git a/README b/README index e7a95367..1a0bfc1a 100644 --- a/README +++ b/README @@ -34,7 +34,11 @@ This README is included with the development version of Privoxy 3.1.1, which will someday become Privoxy v3.2. See http://www.privoxy.org/ for more information. The current code level is technically alpha, but is not yet -significantly different from the 3.0.0 stable branch at this time.. +significantly different from the 3.0.0 stable branch at this time (other +than more bugs). + +There is not much reason to actually run this branch unless you want to help +chase bugs, or with development. ------------------------------------------------------------------------------- @@ -69,56 +73,8 @@ change your browser if upgrading!!! And maybe firewall, etc. 2. INSTALL -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.1.1-beta-src* [.tgz or .tar.gz] - cd privoxy-3.1.1-beta - -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) - -+-----------------------------------------------------------------------------+ -| Warning | -|-----------------------------------------------------------------------------| -|The "make install" target is temporary quite broken! It is recommended to use| -|a binary package, or do a source build, and manually install the components. | -|Sorry. | -+-----------------------------------------------------------------------------+ - -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. - -For binary RPM installation, and other platforms, see the user-manual as well. +See the INSTALL file in this directory, for installing from source, and the +User Manual, for other installation types. ------------------------------------------------------------------------------- -- 2.39.2