will not be overwritten, and the new ones will be installed with a "new"
extension. default.action, default.filter, and standard.action will be
overwritten. You will then need to manually update the other installed
-configuration files as needed. All template files will be overwritten. If you
-have customized, local templates, you should save these first, and in fact it
-is wise to always save any important configuration files "just in case". If a
-previous version of Privoxy is already running, you will have to restart it
-manually.
+configuration files as needed. The default template files will be overwritten.
+If you have customized, local templates, these should be stored safely in a
+separate directory and defined in config by the "templdir" directive. It is of
+course wise to always back-up any important configuration files "just in case".
+If a previous version of Privoxy is already running, you will have to restart
+it manually.
For more detailed instructions on how to build Redhat RPMs, Windows
self-extracting installers, building on platforms with special requirements
Purpose : Entity included in other project documents.
- $Id: buildsource.sgml,v 2.12 2006/11/14 01:57:46 hal9 Exp $
+ $Id: buildsource.sgml,v 2.13 2007/11/14 18:18:15 fabiankeil Exp $
Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
See LICENSE.
This file is included into:
user-manual
- README
+ INSTALL
-->
<para>
these will not be overwritten, and the new ones will be installed with a
<quote>new</quote> extension. default.action, default.filter, and
standard.action <emphasis>will be overwritten</emphasis>. You will then need
- to manually update the other installed configuration files as needed. All
- template files will be overwritten. If you have customized, local templates,
- you should save these first, and in fact it is wise to always save any
+ to manually update the other installed configuration files as needed. The
+ default template files <emphasis>will</emphasis> be overwritten. If you have
+ customized, local templates, these should be stored safely in a separate
+ directory and defined in <filename>config</filename> by the
+ <quote>templdir</quote> directive. It is of course wise to always back-up any
important configuration files <quote>just in case</quote>. If a previous
version of <application>Privoxy</application> is already running, you will
have to restart it manually.
> <DIV
CLASS="TABLE"
><A
-NAME="AEN2168"
+NAME="AEN2171"
></A
><P
><B
><H2
CLASS="SECT2"
><A
-NAME="AEN2267"
+NAME="AEN2270"
>8.1. Finding the Right Mix</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN2274"
+NAME="AEN2277"
>8.2. How to Edit</A
></H2
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2365"
+NAME="AEN2368"
>8.4.1. The Domain Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2436"
+NAME="AEN2439"
>8.4.2. The Path Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4242"
+NAME="AEN4245"
>8.5.39. Summary</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4307"
+NAME="AEN4310"
>8.7.1. default.action</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4443"
+NAME="AEN4446"
>8.7.2. user.action</A
></H3
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN5328"
+NAME="AEN5331"
>14.2. Privoxy's Internal Pages</A
></H2
><P
Privoxy main page:
</P
><A
-NAME="AEN5342"
+NAME="AEN5345"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN5350"
+NAME="AEN5353"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN5355"
+NAME="AEN5358"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN5360"
+NAME="AEN5363"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN5365"
+NAME="AEN5368"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
place:
</P
><A
-NAME="AEN5373"
+NAME="AEN5376"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN5377"
+NAME="AEN5380"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN5380"
+NAME="AEN5383"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><H2
CLASS="SECT2"
><A
-NAME="AEN813"
+NAME="AEN816"
>6.1. Controlling Privoxy with Your Web Browser</A
></H2
><P
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN821"
+NAME="AEN824"
></A
> Privoxy Menu</H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN5071"
+NAME="AEN5074"
>12.1. License</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN4598"
+NAME="AEN4601"
>9.1. Filter File Tutorial</A
></H2
><P
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN813"
+HREF="configuration.html#AEN816"
>Controlling Privoxy with Your Web Browser</A
></DT
><DT
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN2267"
+HREF="actions-file.html#AEN2270"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN2274"
+HREF="actions-file.html#AEN2277"
>How to Edit</A
></DT
><DT
><DL
><DT
>8.4.1. <A
-HREF="actions-file.html#AEN2365"
+HREF="actions-file.html#AEN2368"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN2436"
+HREF="actions-file.html#AEN2439"
>The Path Pattern</A
></DT
><DT
></DT
><DT
>8.5.39. <A
-HREF="actions-file.html#AEN4242"
+HREF="actions-file.html#AEN4245"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN4307"
+HREF="actions-file.html#AEN4310"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN4443"
+HREF="actions-file.html#AEN4446"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN4598"
+HREF="filter-file.html#AEN4601"
>Filter File Tutorial</A
></DT
><DT
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN5071"
+HREF="copyright.html#AEN5074"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN5328"
+HREF="appendix.html#AEN5331"
>Privoxy's Internal Pages</A
></DT
><DD
>will be overwritten</I
></SPAN
>. You will then need
- to manually update the other installed configuration files as needed. All
- template files will be overwritten. If you have customized, local templates,
- you should save these first, and in fact it is wise to always save any
+ to manually update the other installed configuration files as needed. The
+ default template files <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>will</I
+></SPAN
+> be overwritten. If you have
+ customized, local templates, these should be stored safely in a separate
+ directory and defined in <TT
+CLASS="FILENAME"
+>config</TT
+> by the
+ <SPAN
+CLASS="QUOTE"
+>"templdir"</SPAN
+> directive. It is of course wise to always back-up any
important configuration files <SPAN
CLASS="QUOTE"
>"just in case"</SPAN
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN566"
+NAME="AEN569"
></A
><P
><B
><P
></P
>
-
<P
></P
><TABLE
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN621"
+NAME="AEN624"
></A
><P
><B
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN665"
+NAME="AEN668"
></A
><P
><B