[debian-mysql] MariaDB: TokuDB workaround for non amd64-platforms

[Otto Kekäläinen]

2014-02-04 James Page <james.page at ubuntu.com>:
> On 03/02/14 17:55, Otto Kekäläinen wrote:
>> Another thing I noticed while updating MariaDB to .35 is that it
>> now includes a new database engine TokuDB. However it has a cmake
>> rule to build it only on amd64. It has never and will never be
>> ported to i386.
>
> Hmm - this makes me a little uncomfortable - introducing new features
> in point releases does not seem like a great idea;  right new we are
> able to push stable updates for mysql-5.5 because this does not happen.

Upstream says these are "just" plugins and storage engines. We can
drop them from the package and everything else will continue to work
just at is did in earlier point release. Are these kludges acceptable,
can we do better, or do you want me to drop oqgraph and tokudb?

>> Currently the cmake also fiddles with
>> debian/mariadb-server-5.5.install.in to that is is renamed to omit
>> the .in ending and will contain or not the TokuDB files, based on
>> if cmake built them or not.
>
> Does this happen generally in the package?  I prefer that any
> templating/conditional logic that massages the packaging lives in
> debian/rules, not in the upstream cmake/Makefiles.

This is the first time I stumbled across this kind of thing. I don't
know about "generally", I haven't read the source, mostly just focused
on debian/* contents.