Percona provides repositories for yum (RPM packages for Red Hat, CentOS and Amazon Linux AMI) and apt (.deb packages for Ubuntu and Debian) for software such as Percona Server, XtraDB, XtraBackup, and Percona Toolkit. This makes it easy to install and update your software and its dependencies through your operating system’s package manager.

The percona-server-common package contains files common to the
server and client.

The percona-server-client package contains the command line
client.

The percona-server-dfsg package contains....

The libperconaserverclient-dev package contains header files needed to
compile software to use the client library.

The libperconaserverclient18 package contains the client shared
library. The 18 is a reference to the version of the shared
library. The version is incremented when there is a ABI change that
requires software using the client library to be recompiled or their
source code modified.

Percona uses the Bazaar revision
control system for development. To build the latest Percona Server
from the source tree you will need Bazaar installed on your system.

Good practice is to use a shared repository, create one like this:

$ bzr init-repo ~/percona-server

You can now fetch the latest Percona Server 5.5 sources. In the
future, we will provide instructions for fetching each specific
Percona Server version and building it, but currently we will just
talk about building the latest Percona Server 5.5 development tree.

$ cd ~/percona-server
$ bzr branch lp:percona-server/5.5

Fetching all the history of Percona Server 5.5 may take a long time,
up to 20 or 30 minutes is not uncommon.

If you are going to be making changes to Percona Server 5.5 and wanting
to distribute the resulting work, you can generate a new source tarball
(exactly the same way as we do for release):

After either fetching the source repository or extracting a source tarball
(from Percona or one you generated yourself), you will now need to
configure and build Percona Server.

First, run cmake to configure the build. Here you can specify all the normal
build options as you do for a normal MySQL build. Depending on what
options you wish to compile Percona Server with, you may need other
libraries installed on your system. Here is an example using a
configure line similar to the options that Percona uses to produce
binaries:

If you wish to build your own Percona Server Debian/Ubuntu (dpkg) packages,
you first need to start with a source tarball, either from the Percona
website or by generating your own by following the instructions above(
Installing Percona Server from the Bazaar Source Tree).

Put the debian packaging in the directory that Debian expects it to be in:

$ cp -ap build-ps/debian debian

Update the changelog for your distribution (here we update for the unstable
distribution - sid), setting the version number appropriately. The trailing one
in the version number is the revision of the Debian packaging.

You can give different distribution options to dch and sbuild to build binary
packages for all Debian and Ubuntu releases.

Note

PAM Authentication Plugin has been merged into Percona Server in 5.5.24-26.0 but it is not built with the server by default. In order to build the Percona Server with PAM plugin, additional option -DWITH_PAM=ON should be used.

This documentation is developed in Launchpad as part of the Percona Server source code.
If you spotted innacuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.