Author: mcbrown
Date: 2008-06-19 14:54:52 +0200 (Thu, 19 Jun 2008)
New Revision: 10981
Log:
Committing the bzr notes for getting MySQL trees (5.1 only)
Modified:
trunk/refman-5.1/apis-c.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/extending-mysql.xml
trunk/refman-5.1/installing-core.xml
trunk/refman-5.1/news.xml
trunk/refman-5.1/partitioning-guide.xml
trunk/refman-5.1/partitioning.xml
Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/apis-c.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 545 bytes
@@ -11044,7 +11044,7 @@
functions, refer to the file
<filename>tests/mysql_client_test.c</filename>. This file can
be obtained from a MySQL source distribution or from the
- BitKeeper source repository.
+ Bazaar source repository.
</para>
</note>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/dba-core.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 604 bytes
@@ -11381,7 +11381,7 @@
</programlisting>
<para>
- If you are working with BitKeeper and a MySQL development source
+ If you are working with Bazaar and a MySQL development source
tree, the tree doesn't contain
<filename>fill_help_tables.sql</filename>. You can download the
proper file for your version of MySQL from
Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/extending-mysql.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 2, Lines Added: 1, Lines Deleted: 7; 998 bytes
@@ -1799,12 +1799,6 @@
</programlisting>
<para>
- If you are copying files from a BitKeeper source tree,
- <command>cp</command> will display an error message about the
- <filename>SCCS</filename> directory, which you can ignore.
- </para>
-
- <para>
After copying the source files, use the following procedure to
create a plugin library:
</para>
@@ -4210,7 +4204,7 @@
<listitem>
<para>
- You need to obtain the BitKeeper source repository for
+ You need to obtain the Bazaar source repository for
MySQL ¤t-series;. See
<xref linkend="installing-source-tree"/>.
</para>
Modified: trunk/refman-5.1/installing-core.xml
===================================================================
--- trunk/refman-5.1/installing-core.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/installing-core.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 16, Lines Added: 137, Lines Deleted: 185; 20703 bytes
@@ -179,8 +179,8 @@
<listitem>
<para>
- Retrieve MySQL from the BitKeeper tree and build it from
- source. The BitKeeper tree contains the latest developer code.
+ Retrieve MySQL from the Bazaar tree and build it from source.
+ The Bazaar tree contains the latest developer code.
</para>
</listitem>
@@ -582,7 +582,7 @@
<para>
If you want to use the very latest sources containing all
- current patches and bugfixes, you can use one of our BitKeeper
+ current patches and bugfixes, you can use one of our Bazaar
repositories. These are not <quote>releases</quote> as such,
but are available as previews of the code on which future
releases are to be based.
@@ -905,13 +905,13 @@
<listitem>
<para>
- You want to use the latest sources from one of the
- BitKeeper repositories to have access to all current
- bugfixes. For example, if you have found a bug and
- reported it to the MySQL development team, the bugfix is
- committed to the source repository and you can access it
- there. The bugfix does not appear in a release until a
- release actually is issued.
+ You want to use the latest sources from one of the Bazaar
+ repositories to have access to all current bugfixes. For
+ example, if you have found a bug and reported it to the
+ MySQL development team, the bugfix is committed to the
+ source repository and you can access it there. The bugfix
+ does not appear in a release until a release actually is
+ issued.
</para>
</listitem>
@@ -1008,8 +1008,8 @@
We make fixes available as soon as we have identified and
corrected small or non-critical but annoying bugs. The
fixes are available in source form immediately from our
- public BitKeeper repositories, and are included in the
- next release.
+ public Bazaar repositories, and are included in the next
+ release.
</para>
</listitem>
@@ -8415,6 +8415,10 @@
<primary>BitKeeper tree</primary>
</indexterm>
+ <indexterm>
+ <primary>Bazaar tree</primary>
+ </indexterm>
+
<caution>
<para>
You should read this section only if you are interested in
@@ -8425,215 +8429,173 @@
</caution>
<para>
- To obtain our most recent development source tree, first
- download and install the BitKeeper free client if you do not
- have it. The client can be obtained from
- <ulink url="http://www.bitmover.com/bk-client2.0.shar"/>. Note
- that you will need <literal>gcc</literal> and
- <literal>make</literal> to build the BitKeeper free client, and
- <command>patch</command> and <command>tar</command> to
use the
- BitKeeper free client. <emphasis role="deprecated">Note that old
- 1.1 versions of the BitKeeper free client will not
- work!</emphasis>
+ To obtain the most recent development source tree, you first
+ need to download and install Bazaar. You can obtain Bazaar from
+ the <ulink url="http://bazaar-vcs.org">Bazaar VCS
+ Website</ulink>. Bazaar is supported by any platform that
+ supports Python, and is therefore compatible with any Linux,
+ Unix, Windows or Mac OS X host. Instructions for downloading and
+ installing Bazaar on the different platforms are available on
+ the Bazaar website.
</para>
<para>
- To install the BitKeeper client on Unix, use these commands:
+ All MySQL projects are hosted on
+ <ulink url="http://launchpad.net/">Launchpad</ulink>. MySQL
+ projects, including MySQL server, MySQL Workbench and others are
+ available from the
+ <ulink url="http://launchpad.net/~mysql">Sun/MySQL
+ Engineering</ulink> page. For the repositories related only to
+ MySQL server, see the
+ <ulink url="http://launchpad.net/mysql-server">MySQL
+ Server</ulink> page.
</para>
-<programlisting>
-shell> <userinput>/bin/sh bk-client2.0.shar</userinput>
-shell> <userinput>cd bk-client2.0</userinput>
-shell> <userinput>make</userinput>
-</programlisting>
-
<para>
- If you get a <literal>cc: command not found</literal> error,
- invoke this command before running <literal>make</literal>:
+ How you continue with the build process will depend on your
+ platform. On Windows, the build process is different from
+ Unix/Linux. To continue building MySQL on Windows, see
+ <xref linkend="windows-source-build"/>.
</para>
-<programlisting>
-shell> <userinput>make CC=gcc</userinput>
-</programlisting>
-
<para>
- The step above will create the utility <command>bkf</command>,
- which is the BitKeeper free client. You may use the BitKeeper
- free client in the same way as the main client. For more
- information on <command>bkf</command>, use:
+ To build under Unix/Linux, you must have the following tools
+ installed:
</para>
-<programlisting>shell> bkf --help</programlisting>
+ <itemizedlist>
- <para>
- To install the BitKeeper client on Windows, use these
- instructions:
- </para>
-
- <orderedlist>
-
<listitem>
<para>
- Download and install Cygwin from
- <ulink url="http://cygwin.com/">http://cygwin.com</ulink>.
+ GNU <command>make</command>, available from
+ <ulink url="http://www.gnu.org/software/make/"/>. Although
+ some platforms come with their own <command>make</command>
+ implementations, it is highly recommended that you use GNU
+ <command>make</command>. It may already be available on your
+ system as <command>gmake</command>.
</para>
</listitem>
<listitem>
<para>
- Make sure <command>patch</command>,
<command>tar</command>,
- <command>gcc</command> and <command>make</command>
have been
- installed under Cygwin. You can test this by issuing
- <command>which
<replaceable>gcc</replaceable></command> for
- each command. If a required tool is not installed, run
- Cygwin's package manager, select the required tools and
- install them.
+ <command>autoconf</command> 2.58 (or newer), available from
+ <ulink url="http://www.gnu.org/software/autoconf/"/>.
</para>
</listitem>
<listitem>
<para>
- For the installation of the BitKeeper free client, use the
- same installations as given for Unix-like systems above.
+ <command>automake</command> 1.8.1, available from
+ <ulink url="http://www.gnu.org/software/automake/"/>.
</para>
</listitem>
- </orderedlist>
-
- <para>
- To continue building MySQL on Windows, see
- <xref linkend="windows-source-build"/>.
- </para>
-
- <para>
- The BitKeeper free client is shipped with its source code. The
- only documentation available for the free client is the source
- code itself.
- </para>
-
- <para>
- After you have installed the BitKeeper client, you can access
- the MySQL development source tree:
- </para>
-
- <orderedlist>
-
<listitem>
<para>
- Change location to the directory you want to work from, and
- then use the following command to make a local copy of the
- MySQL ¤t-series; branch:
+ <command>libtool</command> 1.5, available from
+ <ulink url="http://www.gnu.org/software/libtool/"/>.
</para>
+ </listitem>
-<programlisting>
-shell> <userinput>bkf clone bk://mysql.bkbits.net/mysql-¤t-series;
mysql-¤t-series;</userinput>
-</programlisting>
-
+ <listitem>
<para>
- In the preceding example, the source tree is set up in the
- <filename>mysql-¤t-series;/</filename> subdirectory of
- your current directory.
+ <command>m4</command>, available from
+ <ulink url="http://www.gnu.org/software/m4/"/>.
</para>
-
- <para>
- The initial download of the source tree may take a while,
- depending on the speed of your connection. Please be
- patient.
- </para>
</listitem>
<listitem>
<para>
- You need GNU <command>make</command>,
- <command>autoconf</command> 2.58 (or newer),
- <command>automake</command> 1.8.1,
- <command>libtool</command> 1.5, and
<command>m4</command> to
- run the next set of commands. Even though many operating
- systems come with their own implementation of
- <command>make</command>, chances are high that the
- compilation fails with strange error messages. Therefore, it
- is highly recommended that you use GNU
- <command>make</command> (sometimes named
- <command>gmake</command>) instead.
+ <command>bison</command>, available from
+ <ulink url="http://www.gnu.org/software/bison/"/>. You
+ should use the latest version of bison where possible.
+ Version 1.75 and version 2.1 are known to work. There have
+ been reported problems with <command>bison</command> 1.875.
+ If you experience problems, upgrade to a later, rather than
+ earlier, version. Versions of <command>bison</command> older
+ than 1.75 may report this error:
</para>
+<programlisting>
+sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded
+</programlisting>
+
<para>
- Fortunately, a large number of operating systems ship with
- the GNU toolchain preinstalled or supply installable
- packages of these. In any case, they can also be downloaded
- from the following locations:
+ The maximum table size is not actually exceeded; the error
+ is caused by bugs in older versions of
+ <command>bison</command>.
</para>
+ </listitem>
- <itemizedlist>
+ </itemizedlist>
- <listitem>
- <para>
- <ulink url="http://www.gnu.org/software/autoconf/"/>
- </para>
- </listitem>
+ <para>
+ Once you have the necessary tools installed, you can follow the
+ process below:
+ </para>
- <listitem>
- <para>
- <ulink url="http://www.gnu.org/software/automake/"/>
- </para>
- </listitem>
+ <orderedlist>
- <listitem>
- <para>
- <ulink url="http://www.gnu.org/software/libtool/"/>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ To obtain a copy of the MySQL source code, you must create a
+ new Bazaar branch. If you do not already have a Bazaar
+ repository directory set up, you need to initialize a new
+ directory:
+ </para>
- <listitem>
- <para>
- <ulink url="http://www.gnu.org/software/m4/"/>
- </para>
- </listitem>
+<programlisting>shell> <userinput>mkdir mysql-server</userinput>
+shell> <userinput>bzr init-repo
mysql-server</userinput></programlisting>
- <listitem>
- <para>
- <ulink url="http://www.gnu.org/software/make/"/>
- </para>
- </listitem>
+ <para>
+ Once you have an initialized directory, you can
+ <literal>branch</literal> from the public MySQL server
+ repositories. To create a branch of a specific version:
+ </para>
- </itemizedlist>
+<programlisting>shell> <userinput>cd mysql-server</userinput>
+shell> <userinput>bzr branch lp:mysql-server/5.1
mysql-5.1</userinput></programlisting>
<para>
- To configure MySQL ¤t-series;, you also need GNU
- <command>bison</command>. You should use the latest version
- of bison where possible. Version 1.75 and version 2.1 are
- known to work. There have been reported problems with
- <command>bison</command> 1.875. If you experience problems,
- upgrade to a later, rather than earlier, version. Versions
- of <command>bison</command> older than 1.75 may report this
- error:
+ The initial download will take some time to complete,
+ depending on the speed of your connection. Please be
+ patient. Once you have downloaded the first tree, additional
+ trees should take significantly less time to download.
</para>
-<programlisting>
-sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded
-</programlisting>
+ <para>
+ When building from the Bazaar branch, you may want to create
+ a copy of your active branch so that you can make
+ configuration and other changes without affecting the
+ original branch contents. You can achieve this by branching
+ from the original branch:
+ </para>
- <note>
- <para>
- The maximum table size is not actually exceeded; the error
- is caused by bugs in older versions of
- <command>bison</command>.
- </para>
- </note>
+<programlisting>shell> <userinput>bzr branch mysql-5.1
mysql-5.1-build</userinput></programlisting>
+ </listitem>
+ <listitem>
<para>
The following example shows the typical commands required to
configure a source tree. The first <literal>cd</literal>
command changes location into the top-level directory of the
tree; replace <filename>mysql-¤t-series;</filename>
- with the appropriate directory name. The second line (for
- <filename>storage/innobase</filename>) is needed only before
- MySQL 5.1.12.
+ with the appropriate directory name.
</para>
+ <note>
+ <para>
+ For MySQL 5.1.12 and earlier, you must separately
+ configure the <literal>INNODB</literal> storage engine.
+ You can do this by running the following command from the
+ main source directory:
+ </para>
+
+<programlisting>shell> <userinput>(cd storage/innobase; autoreconf
--force --install)</userinput></programlisting>
+ </note>
+
<programlisting>
shell> <userinput>cd mysql-¤t-series;</userinput>
-shell> <userinput>(cd storage/innobase; autoreconf --force
--install)</userinput>
shell> <userinput>autoreconf --force --install</userinput>
shell> <userinput>./configure # Add your favorite options
here</userinput>
shell> <userinput>make</userinput>
@@ -8648,7 +8610,6 @@
shell> <userinput>aclocal; autoheader</userinput>
shell> <userinput>libtoolize --automake --force</userinput>
shell> <userinput>automake --force --add-missing; autoconf</userinput>
-shell> <userinput>(cd storage/innobase; aclocal; autoheader; autoconf;
automake)</userinput>
</programlisting>
<para>
@@ -8672,7 +8633,8 @@
<para>
If you get some strange errors during this stage, verify
- that you really have <command>libtool</command> installed.
+ that you have the correct version of the
+ <command>libtool</command> installed.
</para>
<para>
@@ -8731,14 +8693,14 @@
<listitem>
<para>
After initially copying the repository with
- <command>bkf</command> to obtain the source tree, you should
+ <command>bzr</command> to obtain the source tree, you should
use <command>pull</command> option to periodically update
your local copy. To do this any time after you have set up
the repository, use this command:
</para>
<programlisting>
-shell> <userinput>bkf pull</userinput>
+shell> <userinput>bzr pull</userinput>
</programlisting>
</listitem>
@@ -8746,26 +8708,17 @@
<para>
You can examine the changeset comments for the tree by using
the <literal>changes</literal> option to
- <command>bkf</command>:
+ <command>bzr</command>:
</para>
-<programlisting>shell> bkf changes</programlisting>
+<programlisting>shell> bzr log</programlisting>
<para>
- To get a list of the changes that would be applied with the
- next <literal>bkf pull</literal>:
+ You can get a visual representation of the changes by using
+ the <literal>visualize</literal> command.
</para>
-<programlisting>shell> bkf changes -R</programlisting>
-
<para>
- To obtain a patch file for a specific changeset
- (<literal>CSETID</literal>), use:
- </para>
-
-<programlisting>shell> bkf changes
-vvr<replaceable>CSETID</replaceable></programlisting>
-
- <para>
If you see diffs or code that you have a question about, do
not hesitate to send email to the MySQL
<literal>internals</literal> mailing list. See
@@ -8780,8 +8733,7 @@
<para>
You can also browse changesets, comments, and source code
online. To browse this information for MySQL ¤t-series;,
- go to
- <ulink url="http://mysql.bkbits.net:8080/mysql-¤t-series;"/>.
+ go to <ulink url="http://launchpad.net/mysql-server/"/>.
</para>
</section>
@@ -9466,7 +9418,7 @@
These instructions describe how to build binaries from source
for MySQL ¤t-series; on Windows. Instructions are provided
for building binaries from a standard source distribution or
- from the BitKeeper tree that contains the latest development
+ from the Bazaar tree that contains the latest development
source.
</para>
@@ -9474,8 +9426,8 @@
<para>
The instructions here are strictly for users who want to test
MySQL on Microsoft Windows from the latest source distribution
- or from the BitKeeper tree. For production use, MySQL AB does
- not advise using a MySQL server built by yourself from source.
+ or from the Bazaar tree. For production use, MySQL AB does not
+ advise using a MySQL server built by yourself from source.
Normally, it is best to use precompiled binary distributions
of MySQL that are built specifically for optimal performance
on Windows by MySQL AB. Instructions for installing binary
@@ -9528,9 +9480,9 @@
<listitem>
<para>
- If you are compiling from a BitKeeper tree or making changes
- to the parser, you need <literal>bison</literal> for
- Windows, which can be downloaded from
+ If you are compiling from a Bazaar tree or making changes to
+ the parser, you need <literal>bison</literal> for Windows,
+ which can be downloaded from
<ulink url="http://gnuwin32.sourceforge.net/packages/bison.htm"/>.
Download the package labeled <quote>Complete package,
excluding sources</quote>. After installing the package,
@@ -9582,7 +9534,7 @@
<listitem>
<para>
Package a source distribution yourself from the latest
- BitKeeper developer source tree. For instructions on pulling
+ Bazaar developer source tree. For instructions on pulling
the latest source files, see
<xref linkend="installing-source-tree"/>.
</para>
@@ -9650,7 +9602,7 @@
<listitem>
<para>
- If you are installing from a BitKeeper tree, the root
+ If you are installing from a Bazaar tree, the root
directory of that tree is the work directory in the
following instructions.
</para>
Modified: trunk/refman-5.1/news.xml
===================================================================
--- trunk/refman-5.1/news.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/news.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 665 bytes
@@ -49,7 +49,7 @@
<para>
The date mentioned with a release version is the date of the last
- BitKeeper ChangeSet on which the release was based, not the date
+ Bazaar ChangeSet on which the release was based, not the date
when the packages were made available. The binaries are usually made
available a few days after the date of the tagged ChangeSet, because
building and testing all packages takes some time.
Modified: trunk/refman-5.1/partitioning-guide.xml
===================================================================
--- trunk/refman-5.1/partitioning-guide.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/partitioning-guide.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 778 bytes
@@ -407,7 +407,7 @@
MySQL 5.1 binaries are now available from
<ulink url="http://dev.mysql.com/downloads/mysql/5.1.html"/>.
However, for the latest partitioning bugfixes and feature
- additions, you can obtain the source from our BitKeeper
+ additions, you can obtain the source from our Bazaar
repository. To enable partitioning, you need to compile the server
using the <option>--with-partition</option> option. For more
information about building MySQL, see
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2008-06-19 10:25:43 UTC (rev 10980)
+++ trunk/refman-5.1/partitioning.xml 2008-06-19 12:54:52 UTC (rev 10981)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 815 bytes
@@ -148,7 +148,7 @@
MySQL ¤t-series; binaries are available from
<ulink url="&base-url-downloads;mysql/¤t-series;.html"/>.
However, for the latest partitioning bugfixes and feature additions,
- you can obtain the source from our BitKeeper repository. To enable
+ you can obtain the source from our Bazaar repository. To enable
partitioning, you need to compile the server using the
<option>--with-partition</option> option. For more information about
building MySQL, see <xref linkend="installing-source"/>. If you have
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10981 - trunk/refman-5.1 | mcbrown | 19 Jun |