"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "Build.xml" between
shorewall-docs-xml-5.2.3.6.tar.bz2 and shorewall-docs-xml-5.2.6.tar.bz2

About: Shorewall (The Shoreline Firewall) is an iptables based firewall (documentation; XML)

Build.xml  (shorewall-docs-xml-5.2.3.6.tar.bz2):Build.xml  (shorewall-docs-xml-5.2.6.tar.bz2)
skipping to change at line 43 skipping to change at line 43
1.2 or any later version published by the Free Software Foundation; with 1.2 or any later version published by the Free Software Foundation; with
no Invariant Sections, with no Front-Cover, and with no Back-Cover no Invariant Sections, with no Front-Cover, and with no Back-Cover
Texts. A copy of the license is included in the section entitled Texts. A copy of the license is included in the section entitled
<quote><ulink url="GnuCopyright.htm">GNU Free Documentation <quote><ulink url="GnuCopyright.htm">GNU Free Documentation
License</ulink></quote>.</para> License</ulink></quote>.</para>
</legalnotice> </legalnotice>
</articleinfo> </articleinfo>
<note> <note>
<para>This information is provided primarily for Shorewall developers. <para>This information is provided primarily for Shorewall developers.
Users are expected to install from pre-built tarballs or packages.</para> Users are expected to install from pre-built tarballs or packages.
In addition to the below, it is also suggested to read the
<ulink url="https://gitlab.com/shorewall/tools/raw/master/files/shore
wall-release-process.txt">README file</ulink>
located in the root directory of the tools repository.
</para>
</note> </note>
<section> <section>
<title>Git Taxonomy</title> <title>Git Taxonomy</title>
<para>The Shorewall Git tree at Gitlab serves as the master <para>The Shorewall Git tree at Gitlab serves as the master
repository for Shorewall 4.4 and later versions. It is not possible to repository for Shorewall 4.4 and later versions. It is not possible to
simply export a directory from Git and run the simply export a directory from Git and run the
<command>install.sh</command> script in that directory. A build step is <command>install.sh</command> script in that directory. A build step is
required to produce a directory that is suitable for the required to produce a directory that is suitable for the
skipping to change at line 102 skipping to change at line 106
<section> <section>
<title>code/docs</title> <title>code/docs</title>
<para>The stable release XML documents. Depending on the point in the <para>The stable release XML documents. Depending on the point in the
release cycle, these documents may also apply to the current development release cycle, these documents may also apply to the current development
version.</para> version.</para>
</section> </section>
<section> <section>
<title>release (Clone of Release)</title>
<para>Added in Shorewall 4.4.22, this directory contains the files that
contain release-dependent information (change.txt, releasenotes.txt,
.spec files, etc). This is actually a symbolic link to ../release which
has its own Git repository.</para>
</section>
<section>
<title>testing (Clone of Testing)</title>
<para> This directory contains the regression library files.</para>
</section>
<section>
<title>tools (Clone of Tools)</title> <title>tools (Clone of Tools)</title>
<para>This is where the release and build tools are kept. There are four <para>This is where the release and build tools are kept. There are four
subordinate directories:</para> subordinate directories:</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>tools/build</term> <term>tools/build</term>
<listitem> <listitem>
<para>Tools for building and uploading new releases.</para> <para>Tools for building and uploading new releases.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>tools/files</term> <term>tools/files</term>
<listitem> <listitem>
<para>Files that are used during the release process.</para> <para>Files that are used during the release process.
The license and readme files are also kept there.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>tools/testing</term> <term>tools/testing</term>
<listitem> <listitem>
<para>Tools for testing.</para> <para>Tools for testing.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
skipping to change at line 148 skipping to change at line 168
</varlistentry> </varlistentry>
</variablelist> </variablelist>
</section> </section>
<section> <section>
<title>web (Clone of Web)</title> <title>web (Clone of Web)</title>
<para>The files from the web site that are maintained in HTML format. <para>The files from the web site that are maintained in HTML format.
are kept in this directory.</para> are kept in this directory.</para>
</section> </section>
<section>
<title>release (Clone of Release)</title>
<para>Added in Shorewall 4.4.22, this directory contains the files that
contain release-dependent information (change.txt, releasenotes.txt,
.spec files, etc). This is actually a symbolic link to ../release which
has its own Git repository.</para>
</section>
</section> </section>
<section> <section>
<title>Build Tools</title> <title>Build Tools</title>
<para>As described above, the build tools are kept in <filename <para>As described above, the build tools are kept in <filename
class="directory">tools/build.</filename> They are described in the class="directory">tools/build.</filename> They are described in the
following sections.</para> following sections.</para>
<section> <section>
skipping to change at line 183 skipping to change at line 194
<blockquote> <blockquote>
<para><command>setversion</command> <para><command>setversion</command>
<replaceable>version</replaceable></para> <replaceable>version</replaceable></para>
</blockquote> </blockquote>
<para>The <replaceable>version</replaceable> may either be a minor <para>The <replaceable>version</replaceable> may either be a minor
version or a patch version.</para> version or a patch version.</para>
</section> </section>
<section> <section>
<title>build45, build46 and build50</title> <title>build45, build46, and build</title>
<para>These are the scripts that respectively build Shorewall 4.5, <para>These are the scripts that respectively build Shorewall 4.5,
Shorewall 4.6 and Shorewall 5.[012] packages from Git.</para> Shorewall 4.6 and Shorewall 5.[012] packages from Git.
Build is actually a symlink to the current build script.</para>
<para>The scripts copy content from Git using the <command>git <para>The scripts copy content from Git using the <command>git
archive</command> command. They then use that content to build the archive</command> command. They then use that content to build the
packages. In addition to the usual Gnu utilities, the following software packages. In addition to the usual Gnu utilities, the following software
is required:</para> is required:</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>rpmbuild</term> <term>rpmbuild</term>
skipping to change at line 300 skipping to change at line 312
<para>The scripts assume that there will be a separate <firstterm>build <para>The scripts assume that there will be a separate <firstterm>build
directory</firstterm> per major release. Each build directory should directory</firstterm> per major release. Each build directory should
contain the empty file <filename>shorewall-pkg.config</filename>; that contain the empty file <filename>shorewall-pkg.config</filename>; that
file is no longer used but has been retained just as a guard against file is no longer used but has been retained just as a guard against
initiating a build in an unintended directory. To build a release, you initiating a build in an unintended directory. To build a release, you
cd to the appropriate directory and run the build script.</para> cd to the appropriate directory and run the build script.</para>
<para>The general form of the build command is:</para> <para>The general form of the build command is:</para>
<blockquote> <blockquote>
<para><command>build</command>xx [ -<replaceable>options</replaceable> <para><command>build</command>[<replaceable>xx</replaceable>] [ -<r eplaceable>options</replaceable>
] <replaceable>release</replaceable> [ <replaceable>prior ] <replaceable>release</replaceable> [ <replaceable>prior
release</replaceable> ]</para> release</replaceable> ]</para>
</blockquote> </blockquote>
<para>where</para> <para>where</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>opt<emphasis>i</emphasis>ons</term> <term>opt<emphasis>i</emphasis>ons</term>
skipping to change at line 435 skipping to change at line 447
patches against 4.5.7:</para> patches against 4.5.7:</para>
<blockquote> <blockquote>
<para><command>build45 -trc 4.5.7.1 4.5.7</command></para> <para><command>build45 -trc 4.5.7.1 4.5.7</command></para>
</blockquote> </blockquote>
</section> </section>
<section> <section>
<title>upload</title> <title>upload</title>
<para>This script is used to upload a release to www.shorewall.org. The <para>This script is used to upload a release to https://shorewall.org. Th e
command is run in the build directory for the minor release of the command is run in the build directory for the minor release of the
product.</para> product.</para>
<blockquote> <blockquote>
<para><command>upload</command> [ -<replaceable>products</replaceable> <para><command>upload</command> [ -<replaceable>products</replaceable>
] <replaceable>release</replaceable></para> ] <replaceable>release</replaceable></para>
</blockquote> </blockquote>
<para>where</para> <para>where</para>
 End of changes. 8 change blocks. 
15 lines changed or deleted 28 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)