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

[Clint Byrum]

Excerpts from James Page's message of 2014-02-03 22:23:01 -0800:
> Hash: SHA256
> 
> Hi Otto
> 
> 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.
> 

To be fair, we also have access to the bug tracker and code trees with
full explanations of each change, so we can do this "the old way" and
backport each patch.

> > 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.
> 

Agreed, upstream should not be twiddling debian dir things, it will just
confuse us all. I suggest patching that out, and submitting the patch
as a bug upstream. We can do our own version of the .in mangling in the
debian rules.

Upstream is perfectly fine twiddling their own files of course.