Skip navigation links
2.1.2.3 How and When Updates Are Released »
Section Navigation      [Toggle]

2.1.2.2. Choosing a Distribution Format

After choosing which version of MySQL to install, you should decide whether to use a binary distribution or a source distribution. In most cases, you should probably use a binary distribution, if one exists for your platform. Binary distributions are available in native format for many platforms, such as RPM files for Linux or PKG package installers for Mac OS X or Solaris. Distributions also are available as Zip archives or compressed tar files.

Reasons to choose a binary distribution include the following:

  • Binary distributions generally are easier to install than source distributions.

  • To satisfy different user requirements, we provide two different binary versions. One is compiled with the core feature set. The other (MySQL-Max) is compiled with an extended feature set. Both versions are compiled from the same source distribution. All native MySQL clients can connect to servers from either MySQL version.

    The extended MySQL binary distribution is identified by the -max suffix and is configured with the same options as mysqld-max. See Section 5.2, “The mysqld-max Extended MySQL Server”.

    For RPM distributions, if you want to use the MySQL-Max RPM, you must first install the standard MySQL-server RPM.

Under some circumstances, you may be better off installing MySQL from a source distribution:

  • You want to install MySQL at some explicit location. The standard binary distributions are ready to run at any installation location, but you might require even more flexibility to place MySQL components where you want.

  • You want to configure mysqld to ensure that features are available that might not be included in the standard binary distributions. Here is a list of the most common extra options that you may want to use to ensure feature availability:

    • --with-berkeley-db (not available on all platforms)

    • --with-raid

    • --with-libwrap

    • --with-named-z-libs (this is done for some of the binaries)

    • --with-debug[=full]

  • You want to configure mysqld without some features that are included in the standard binary distributions. For example, distributions normally are compiled with support for all character sets. If you want a smaller MySQL server, you can recompile it with support for only the character sets you need.

  • You have a special compiler (such as pgcc) or want to use compiler options that are better optimized for your processor. Binary distributions are compiled with options that should work on a variety of processors from the same processor family.

  • 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.

  • You want to read (or modify) the C and C++ code that makes up MySQL. For this purpose, you should get a source distribution, because the source code is always the ultimate manual.

  • Source distributions contain more tests and examples than binary distributions.


User Comments

Posted by vikas kedia on March 25 2004 5:29am[Delete] [Edit]

If you choose the binary method of install from between binary and source installation method, you have to choose how you want to install the binary:
1. RPM method
2. download the tar.gz file and then just untar it


The factors to consider are:

1. The directory layout which you are comfortable with since the above two binary installation methods give two different directory layouts.

take a look at the directory layouts under the two different binary installation methods at:
http://www.mysql.com/doc/en/Installation_layouts.html

2. The rpm method will give you a startup script and place it in the appropriate location (for e.g in case of redhat it is /etc/rc.d/init.d/mysql) and also make the chkconfig entries in the various run levels. But the tar.gz binary distribution method will not make a startup script and it will also not make the entries in the appropriate run levels. If you do decide to go the tar.gz binary distribution method you will need a startup script. You can see a sample script at http://www.grmtech.com/mysql/samplestartup.html

Though the 2nd point of consideration may seem like a disadvantage for the tar binary install you might want to consider deeply the tar binary installs advantage of having all the mysql related files under one directory and not spread across multiple directories.

Add your own comment.