<link rel="NEXT" title="Update the Webserver" href="webserver-update.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <style type="text/css">
-body {
- background-color: #EEEEEE;
- color: #000000;
- }
- :link { color: #0000FF }
- :visited { color: #840084 }
- :active { color: #0000FF }
- tt.c5 {font-style: italic}
- td.c4 {font-weight: bold}
- table.c3 {background-color: #E0E0E0}
- span.c2 {font-style: italic}
- hr.c1 {text-align: left}
- </style>
</head>
-<body class="SECT1">
+<body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
+"#840084" alink="#0000FF">
<div class="NAVHEADER">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
"webserver-update.html" accesskey="N">Next</a></td>
</tr>
</table>
- <hr class="c1" width="100%">
+ <hr align="left" width="100%">
</div>
<div class="SECT1">
being committed. Stable branches will then have their version
reported as <tt class="LITERAL">0.0.0</tt>, during that period
between releases when changes are being added. This is to denote
- that this code is <span class="emphasis EMPHASIS c2">not for
- release</span>. Then as the release nears, the version is bumped
- according: e.g. <tt class="LITERAL">3.0.1 -> 0.0.0 ->
+ that this code is <span class="emphasis"><i class="EMPHASIS">not
+ for release</i></span>. Then as the release nears, the version is
+ bumped according: e.g. <tt class="LITERAL">3.0.1 -> 0.0.0 ->
3.0.2</tt>.</p>
</li>
</ul>
-> 3.0.1 -> 3.0.2, etc are all stable releases from within the
stable branch. 3.1.x is currently the main trunk, and where work on
3.2.x is taking place. If any questions, please post to the devel list
- <span class="emphasis EMPHASIS c2">before</span> committing to a stable
- branch!</p>
+ <span class="emphasis"><i class="EMPHASIS">before</i></span> committing
+ to a stable branch!</p>
<p>Developers should remember too that if they commit a bugfix to the
stable branch, this will more than likely require a separate submission
to the main trunk, since these are separate development trees within
CVS. If you are working on both, then this would require at least two
- separate check outs (i.e main trunk, <span class=
- "emphasis EMPHASIS c2">and</span> the stable release branch, which is
+ separate check outs (i.e main trunk, <span class="emphasis"><i class=
+ "EMPHASIS">and</i></span> the stable release branch, which is
<tt class="LITERAL">v_3_0_branch</tt> at the moment).</p>
</div>
<h2 class="SECT2"><a name="BEFORERELEASE" id="BEFORERELEASE">6.2.
Before the Release: Freeze</a></h2>
- <p>The following <span class="emphasis EMPHASIS c2">must be done by one
- of the developers</span> prior to each new release.</p>
+ <p>The following <span class="emphasis"><i class="EMPHASIS">must be
+ done by one of the developers</i></span> prior to each new release.</p>
<ul>
<li>
last release (i.e. software release or standalone actions file
release), bump up its version info to A.B in this line:</p>
- <table class="c3" border="0" width="90%">
+ <table border="0" bgcolor="#E0E0E0" width="90%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</li>
<li>
- <p><span class="emphasis EMPHASIS c2">Commit all files that were
- changed in the above steps!</span></p>
+ <p><span class="emphasis"><i class="EMPHASIS">Commit all files that
+ were changed in the above steps!</i></span></p>
</li>
<li>
GPL reasons the first package to be released is always the source
tarball.</p>
- <p>For <span class="emphasis EMPHASIS c2">all</span> types of packages,
- including the source tarball, <span class="emphasis EMPHASIS c2">you
- must make sure that you build from clean sources by exporting the right
- version from CVS into an empty directory</span> (just press return when
- asked for a password):</p>
+ <p>For <span class="emphasis"><i class="EMPHASIS">all</i></span> types
+ of packages, including the source tarball, <span class=
+ "emphasis"><i class="EMPHASIS">you must make sure that you build from
+ clean sources by exporting the right version from CVS into an empty
+ directory</i></span> (just press return when asked for a password):</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</tr>
</table>
- <p><span class="emphasis EMPHASIS c2">Do NOT change</span> a single
- bit, including, but not limited to version information after export
- from CVS. This is to make sure that all release packages, and with
- them, all future bug reports, are based on exactly the same code.</p>
+ <p><span class="emphasis"><i class="EMPHASIS">Do NOT change</i></span>
+ a single bit, including, but not limited to version information after
+ export from CVS. This is to make sure that all release packages, and
+ with them, all future bug reports, are based on exactly the same
+ code.</p>
<div class="WARNING">
<table class="WARNING" border="1" width="100%">
<tr>
- <td class="c4" align="center">Warning</td>
+ <td align="center"><b>Warning</b></td>
</tr>
<tr>
"PACK-GUIDELINES">6.3.1. Note on Privoxy Packaging</a></h3>
<p>Please keep these general guidelines in mind when putting together
- your package. These apply to <span class=
- "emphasis EMPHASIS c2">all</span> platforms!</p>
+ your package. These apply to <span class="emphasis"><i class=
+ "EMPHASIS">all</i></span> platforms!</p>
<ul>
<li>
<p><span class="APPLICATION">Privoxy</span> <span class=
- "emphasis EMPHASIS c2">requires</span> write access to: all
- <tt class="FILENAME">*.action</tt> files, all logfiles, and the
- <tt class="FILENAME">trust</tt> file. You will need to determine
- the best way to do this for your platform.</p>
+ "emphasis"><i class="EMPHASIS">requires</i></span> write access
+ to: all <tt class="FILENAME">*.action</tt> files, all logfiles,
+ and the <tt class="FILENAME">trust</tt> file. You will need to
+ determine the best way to do this for your platform.</p>
</li>
<li>
<h3 class="SECT3"><a name="NEWRELEASE-TARBALL" id=
"NEWRELEASE-TARBALL">6.3.2. Source Tarball</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then run:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then do:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>To upload the package to Sourceforge, simply issue</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<h3 class="SECT3"><a name="NEWRELEASE-RPM" id="NEWRELEASE-RPM">6.3.3.
SuSE, Conectiva or Red Hat RPM</a></h3>
- <p>In following text, replace <tt class="REPLACEABLE c5">dist</tt>
- with either <span class="QUOTE">"rh"</span> for Red Hat or
- <span class="QUOTE">"suse"</span> for SuSE.</p>
+ <p>In following text, replace <tt class=
+ "REPLACEABLE"><i>dist</i></tt> with either <span class=
+ "QUOTE">"rh"</span> for Red Hat or <span class="QUOTE">"suse"</span>
+ for SuSE.</p>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above).</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages"
+ above).</p>
<p>As the only exception to not changing anything after export from
CVS, now examine the file <tt class=
- "FILENAME">privoxy-</tt><tt class="REPLACEABLE c5">dist</tt><tt class="FILENAME">.spec</tt>
+ "FILENAME">privoxy-</tt><tt class="REPLACEABLE"><i>dist</i></tt><tt class="FILENAME">.spec</tt>
and make sure that the version information and the RPM release number
are correct. The RPM release numbers for each version start at one.
Hence it must be reset to one if this is the first RPM for <tt class=
- "REPLACEABLE c5">dist</tt> which is built from version X.Y.Z. Check
- the <a href=
+ "REPLACEABLE"><i>dist</i></tt> which is built from version X.Y.Z.
"http://sourceforge.net/project/showfiles.php?group_id=11118" target=
"_top">file list</a> if unsure. Else, it must be set to the highest
already available RPM release number for that version plus one.</p>
<p>Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then do</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
- make <tt class="REPLACEABLE c5">dist</tt>-dist
+ make <tt class="REPLACEABLE"><i>dist</i></tt>-dist
</pre>
</td>
</tr>
<p>To upload the package to Sourceforge, simply issue</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
- make <tt class="REPLACEABLE c5">dist</tt>-upload <tt class=
-"REPLACEABLE c5">rpm_packagerev</tt>
+ make <tt class="REPLACEABLE"><i>dist</i></tt>-upload <tt class=
+"REPLACEABLE"><i>rpm_packagerev</i></tt>
</pre>
</td>
</tr>
</table>
- <p>where <tt class="REPLACEABLE c5">rpm_packagerev</tt> is the RPM
- release number as determined above. Go to the displayed URL and
+ <p>where <tt class="REPLACEABLE"><i>rpm_packagerev</i></tt> is the
+ RPM release number as determined above. Go to the displayed URL and
release the file publicly on Sourceforge. Use the release notes and
change log from the source tarball package.</p>
</div>
<h3 class="SECT3"><a name="NEWRELEASE-OS2" id="NEWRELEASE-OS2">6.3.4.
OS/2</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then get the OS/2
- Setup module:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then get the OS/2 Setup module:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
directory. Edit the os2build.cmd file to set the final executable
filename. For example,</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
release number matches in the <tt class="FILENAME">PACKAGEID</tt>
section:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>You're now ready to build. Run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Login to Sourceforge's compilefarm via ssh:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</table>
<p>Choose the right operating system (not the Debian one). When
- logged in, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then run:</p>
+ logged in, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then run</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
"_top">http://www.cygwin.com/</a>). Run the following commands from
within a Cygwin bash shell.</p>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then get the Windows
- setup module:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then get the Windows setup module:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
controlled by <tt class="FILENAME">winsetup/GNUmakefile</tt>. All you
need to do is:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<h3 class="SECT3"><a name="NEWRELEASE-DEBIAN" id=
"NEWRELEASE-DEBIAN">6.3.7. Debian</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then add a log entry
- to <tt class="FILENAME">debian/changelog</tt>, if it is not already
- there, for example by running:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then add a log entry to <tt class="FILENAME">debian/changelog</tt>,
+ if it is not already there, for example by running:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
- debchange -v 3.0.20-UNRELEASED-1 "New upstream version"
+ debchange -v 3.0.21-UNRELEASED-1 "New upstream version"
</pre>
</td>
</tr>
<p>Then, run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</table>
<p>This will create <tt class=
- "FILENAME">../privoxy_3.0.20-UNRELEASED-1_i386.deb</tt> which can be
+ "FILENAME">../privoxy_3.0.21-UNRELEASED-1_i386.deb</tt> which can be
uploaded. To upload the package to Sourceforge, simply issue</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<h3 class="SECT3"><a name="NEWRELEASE-MACOSX" id=
"NEWRELEASE-MACOSX">6.3.8. Mac OS X</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above).</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages"
+ above).</p>
<p>There are three modules available in the CVS repository for use on
Mac OS X, though technically only two of them generate a release (the
as follows into a folder parallel to the exported privoxy
source:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
"OS-X-OSXSETUP-MODULE">6.3.8.2. osxsetup module
(DEPRECATED)</a></h4>
- <p><span class="emphasis EMPHASIS c2">This module is deprecated
- since the installer it generates places all Privoxy files in one
- folder in a non-standard location, and supports only Intel Macs
- running OS X 10.6 or higher.</span></p>
+ <p><span class="emphasis"><i class="EMPHASIS">This module is
+ deprecated since the installer it generates places all Privoxy
+ files in one folder in a non-standard location, and supports only
+ Intel Macs running OS X 10.6 or higher.</i></span></p>
<p>Check out the module from CVS as follows into a folder parallel
to the exported privoxy source:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
package name, you can then create the distributable zip file with
the command:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Check out the module from CVS as follows into a folder parallel
to the exported privoxy source:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>The module contains complete instructions on its usage in its
<tt class="FILENAME">README</tt> file. The end result will be the
- the exported version of Privoxy installed on the build machine.</p>
+ exported version of Privoxy installed on the build machine.</p>
</div>
</div>
<p>Login to Sourceforge's compile-farm via ssh:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</table>
<p>Choose the right operating system. When logged in, <span class=
- "emphasis EMPHASIS c2">make sure that you have freshly exported the
- right version into an empty directory</span>. (See "Building and
- releasing packages" above). Then run:</p>
+ "emphasis"><i class="EMPHASIS">make sure that you have freshly
+ exported the right version into an empty directory</i></span>. (See
+ "Building and releasing packages" above). Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<h3 class="SECT3"><a name="NEWRELEASE-HPUX" id=
"NEWRELEASE-HPUX">6.3.10. HP-UX 11</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then run:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<h3 class="SECT3"><a name="NEWRELEASE-AMIGA" id=
"NEWRELEASE-AMIGA">6.3.11. Amiga OS</a></h3>
- <p>First, <span class="emphasis EMPHASIS c2">make sure that you have
- freshly exported the right version into an empty directory</span>.
- (See "Building and releasing packages" above). Then run:</p>
+ <p>First, <span class="emphasis"><i class="EMPHASIS">make sure that
+ you have freshly exported the right version into an empty
+ directory</i></span>. (See "Building and releasing packages" above).
+ Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Login to Sourceforge's compilefarm via ssh:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
</table>
<p>Choose the right operating system. When logged in, <span class=
- "emphasis EMPHASIS c2">make sure that you have freshly exported the
- right version into an empty directory</span>. (See "Building and
- releasing packages" above). Then run:</p>
+ "emphasis"><i class="EMPHASIS">make sure that you have freshly
+ exported the right version into an empty directory</i></span>. (See
+ "Building and releasing packages" above). Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
<p>Then run:</p>
- <table class="c3" border="0" width="100%">
+ <table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
<pre class="PROGRAMLISTING">
column, and click <tt class="LITERAL">Add Release</tt>. You will then
need to create a new release for your package, using the format of
<tt class="LITERAL">$VERSION ($CODE_STATUS)</tt>, e.g. <span class=
- "emphasis EMPHASIS c2">3.0.20 (beta)</span>.</p>
+ "emphasis"><i class="EMPHASIS">3.0.21 (beta)</i></span>.</p>
<p>Now just follow the prompts. Be sure to add any appropriate Release
notes. You should see your freshly uploaded packages in <span class=
</div>
<div class="NAVFOOTER">
- <hr class="c1" width="100%">
+ <hr align="left" width="100%">
<table summary="Footer navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
projects / privoxy.git / blobdiff