Hot on the heels of this week's Drizzle 2012.01.30 source release, we are now also releasing beta quality binary RPMs for your downloading and testing pleasure! While we are revitalizing the Drizzle yum repository, you can download the rpm-bundle from our Launchpad project page: https://launchpad.net/pkg-drizzle/+download
As the Fremont development cycle is ending it's beta cycle and heading for release candidates, we are starting to publish also binary packages for downloads. Today we are releasing RPM packages for RHEL/CentOS 6.0. Fedora 16 packaging has unfortunately been postponed. We will eventually support also Fedora 16 RPMs, but in the mean time you can possibly spot some Drizzle developers on twitter or irc making snarky comments about systemd ...
In the following week(s) we will also publish Debian and Ubuntu packages.
Note that these packages are a first release of their kind and still a bit experimental. What this means is that the underlying Drizzle release itself is stabilizing quite nicely, but the packaging process is currently not completely integrated nor automated.
Please report errors at the main Drizzle bug tracker, and direct your general feedback to the drizzle-discuss mailing list.
Details:
- These packages were built from the Drizzle bzr trunk at tag 2012.01.30.
- In addition a branch that supports "make rpm" was merged from lp:~hingo/drizzle/drizzle-integrate-packaging-rpm. This is based on the same RPM spec as was used for Drizzle 7, but the intent is to integrate it with the main Drizzle source code and then Jenkins builds. The current release was however still a manual process.
- When building this way, an additional bzr tag --force 2012.01.30 was needed to maintain the same version number.
- Along the RPMs we have uploaded a source tar file fake-drizzle7-
2012.01. 30.tar. gz. This corresponds to the real Drizzle 2012.01.30 release, plus the above changes. - The RPM files are made available as a tar bundle. The process to publish into the Drizzle yum repository is currently broken but will resume in the near future.
- A related issue is that the packages are not signed.
- Known issue: If you install the plugin rpms, they will be automatically loaded at startup. However, some of them (in particular, many auth plugins, the policy plugins and possibly the slave plugin) don't actually work without further configuration and will thus prevent the server from starting. If you encounter this plugin, you should either complete the configuration (in /etc/drizzle/conf.d/[plugin].conf) or, if you don't want to use it, uninstall the plugin.