projects
/
privoxy.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Adjust a couple of asterisks
[privoxy.git]
/
INSTALL
diff --git
a/INSTALL
b/INSTALL
index
67995e5
..
8018fae
100644
(file)
--- a/
INSTALL
+++ b/
INSTALL
@@
-39,8
+39,8
@@
compiler like gcc are required.
When building from a source tarball, first unpack the source:
When building from a source tarball, first unpack the source:
- tar xzvf privoxy-3.0.
27
-beta-src.tar.gz
- cd privoxy-3.0.
27
-beta
+ tar xzvf privoxy-3.0.
32
-beta-src.tar.gz
+ cd privoxy-3.0.
32
-beta
To build the development version, you can get the source code by doing:
To build the development version, you can get the source code by doing:
@@
-50,7
+50,7
@@
To build the development version, you can get the source code by doing:
This will create a directory named <root-dir>/privoxy/, which will contain the
source tree.
This will create a directory named <root-dir>/privoxy/, which will contain the
source tree.
-Note that source code in G
IT
is development quality, and may not be stable or
+Note that source code in G
it
is development quality, and may not be stable or
well tested.
It is strongly recommended to not run Privoxy as root. You should configure/
well tested.
It is strongly recommended to not run Privoxy as root. You should configure/
@@
-69,7
+69,7
@@
And then /etc/group, like:
Some binary packages may do this for you.
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
autoheader
autoconf