Commit 17205179 authored by Michael Graff's avatar Michael Graff

reword some parts, indent properly

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@1538 e5f2f494-b856-4b98-b285-d166d9295462
parent 07cc9207
......@@ -376,7 +376,13 @@ var/
<section>
<title>Download Tar File</title>
<para>The BIND 10 releases are available as tar file downloads from
<para>
Downloading a release tar file is the recommended method to
obtain the source code.
</para>
<para>
The BIND 10 releases are available as tar file downloads from
<ulink url="ftp://ftp.isc.org/isc/bind10/"/>.
Periodic development snapshots may also be available.
</para>
......@@ -385,6 +391,12 @@ var/
<section>
<title>Retrieve from Subversion</title>
<para>
Downloading this "bleeding edge" code is recommended only for
developers or advanced users. Using development code in a production
environment is not recommended.
</para>
<para>
The latest development code, including temporary experiments
and un-reviewed code, is available via the BIND 10 code revision
......@@ -400,40 +412,37 @@ var/
<screen>$ <userinput>svn co svn://bind10.isc.org/svn/bind10/trunk</userinput></screen>
</para>
<para>
You do not need to retrieve the source code from subversion
unless you are testing latest code which is not provided in the
source tar file or you are a developer.
Most users will just use the source tar file.
</para>
<section>
<title>Generate configuration files</title>
<para>
When checking out the code from
the code version control system, it doesn't include the
generated configure script, Makefile.in files, nor the
related configure files.
They can be created by running <command>autoreconf</command>
with the <option>--install</option> switch.
This will run <command>autoconf</command>, <command>aclocal</command>,
<command>libtoolize</command>, <command>autoheader</command>,
<command>automake</command>, and related commands &mdash;
and provide needed build files.
</para>
<para>
This requires <command>autoconf</command> version 2.59 or newer
and <command>automake</command> version 1.10 or better.
(For working Python 3.1 tests, <command>automake</command>
version 1.11 or better is needed or use the
<option>--with-pythonpath</option> configure option described
below).
</para>
<note><para>
Some operating systems do not provide these in their
default installation nor standard packages collections.
You may need to install them separately.
</para></note>
When checking out the code from
the code version control system, it doesn't include the
generated configure script, Makefile.in files, nor the
related configure files.
They can be created by running <command>autoreconf</command>
with the <option>--install</option> switch.
This will run <command>autoconf</command>,
<command>aclocal</command>,
<command>libtoolize</command>,
<command>autoheader</command>,
<command>automake</command>,
and related commands.
</para>
<para>
This requires <command>autoconf</command> version 2.59 or newer
and <command>automake</command> version 1.10 or better.
(For working Python 3.1 tests, <command>automake</command>
version 1.11 or better is needed or use the
<option>--with-pythonpath</option> configure option described
below).
</para>
<note>
<para>
Some operating systems do not provide these in their
default installation nor standard packages collections.
You may need to install them separately.
</para>
</note>
</section>
</section>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment