Drizzle - A Microkernel DBMS for High Performance Scale-Out Applications
Blog | Bugs | Build Farm | Events | Feature Requests | IRC | LCOV | Mailing List | Planet Drizzle | Source Code | User Docs | Twitter

Contents 1 Fedora/RHEL 2 Debian/Ubuntu 3 FreeBSD 4 Gentoo

Fedora/RHEL

• See: RPM Installation Fedora/RHEL

Debian/Ubuntu

For Drizzle, see the Debian or Ubuntu package info.

• To install the necessary tools and libraries to build Drizzle:

% sudo apt-get install python-software-properties
% sudo add-apt-repository ppa:drizzle-developers/ppa
% sudo apt-get update
% sudo apt-get install drizzle-dev

• Binary packages are created from each Bi-weekly releases of Drizzle. To add this repository and install Drizzle:

% sudo add-apt-repository ppa:drizzle-developers/ppa
% sudo apt-get update
% sudo apt-get install drizzle

• All merges into Drizzle trunk have a hudson job which creates a source package and uploads the source package to the launchpad builder
• Once launchpad builds the package, it'll be in the trunk packages ppa. To add this repository and install Drizzle:

% sudo add-apt-repository ppa:drizzle-developers/trunk
% sudo apt-get update
% sudo apt-get install drizzle

There are three Drizzle debian packaging branches:

• lp:~drizzle-developers/drizzle/dpkg
• lp:~drizzle-developers/drizzle/debian
• lp:~drizzle-developers/drizzle/nightly

dpkg is where all packaging code work should go in between releases.

When it's time to release, that work should be merged in to debian, the release should be produced, and debian should be merged back into dpkg.

Any time changes are made to dpkg, they should be merged into nightly. Hudson does automated building from nightly and pushes back to it, but there is really no reason to every merge _from_ nightly into anything else. If hudson packaging hits a snag that needs new packaging control that work goes into dpkg and then into nightly.

FreeBSD

• See the FreeBSD ports listing

Gentoo

• See the Gentoo portage listing