Excerpts from Ross Timson's message of 2013-04-29 09:46:32 UTC:
> Is this still being worked on?
>
Not to my knowledge, no.
> What are the packaging issues mentioned as there seems to be official
> repos for Precise available?
>
Percona seems to be more careful about dependencies and maintainer
scripts, so that one can go back to stock MySQL from Percona.
MariaDB's packaging produced an issue where I could not go back to stock
MySQL or to Percona Server from MariaDB.
Right now, I'm more convinced that charms need includes of some kind, so
that the 99% of code that the charms will share can be in one charm, and
then just include the slight differences for maria/percona/stock mysql.
> I'm new to Juju so apologies if I'm missing something obvious here.
> More and more big players are switching to MariaDB (eg Wikipedia did
> recently) and I'd love to see this option added.
>
You're welcome to dive in and try to solve this. For now, stock MySQL
and Percona are the only options.
Excerpts from Ross Timson's message of 2013-04-29 09:46:32 UTC:
> Is this still being worked on?
>
Not to my knowledge, no.
> What are the packaging issues mentioned as there seems to be official
> repos for Precise available?
>
Percona seems to be more careful about dependencies and maintainer
scripts, so that one can go back to stock MySQL from Percona.
MariaDB's packaging produced an issue where I could not go back to stock
MySQL or to Percona Server from MariaDB.
Right now, I'm more convinced that charms need includes of some kind, so
that the 99% of code that the charms will share can be in one charm, and
then just include the slight differences for maria/percona/stock mysql.
> I'm new to Juju so apologies if I'm missing something obvious here.
> More and more big players are switching to MariaDB (eg Wikipedia did
> recently) and I'd love to see this option added.
>
You're welcome to dive in and try to solve this. For now, stock MySQL
and Percona are the only options.