kdelibs4::FindMySQL.cmake

[RJVB (René Bertin)]

Building a new Calligra version I ran into an issue with the cmake macro for finding the MySQL libraries when one has port:mariadb installed instead of a "regular" mysql port -- and that's actually the default with port:akonadi.

I'm attaching a patch that adds support for the mysql libraries provided by MariaDB (and underlines once more that too much sandboxing/compartmentalisation has undesirable implications). The patch will require a corresponding post-patch in the kdelibs Portfile, of course:

post-patch {
    reinplace "s|%PREFIX%|${prefix}|g" \
        ${worksrcpath}/cmake/modules/FindMySQL.cmake
}

[RJVB (René Bertin)]

I spoke a tad too soon (Calligra takes a "while" to build); the KDE4 portgroup had to be edited too.

I'm not sure whether it should define the executables, or whether those should be left unset and resolved by the user doing a port select. The definitions seem clearly unnecessary: I don't have ${prefix}/bin/mysql_config5 nor ${prefix}/libexec/mysqld, and yet everything always worked as far as I can tell.

[mkae (Marko Käning)]

Cc Me!

[NicosPavlov]

I fully agree on the paths which are completely obsolete in the PortGroup. I removed them in r142093.

On the other hand, I am not sure about the changes in FindMySQL. First, if they are performed, they should be more general than just for the two ports included (mysql5 and mariadb). Each SQL port and its variants (such as mysql55, mysql56, mariadb55, percona56, ...) create their own subdirectories, which should be taken into account. I am also not that sure about the usefulness of that script. Akonadi, for example, is defining its own variants (as most ports using MySQL and its derivatives) and own paths anyway. I'll have to look into it a bit more to see how used it is.

[RJVB (René Bertin)]

Evidently my patches to FindMySQL have a bit the character of an example. They show how to address the situation in a way that makes things build in my set-up and in what may or may not be the most common set-ups. I haven't even tried to check all possible alternatives that could be added. I agree it should be done, but I'm not convinced it's necessary to be exhaustive immediately (= one could wait for further reports).

Meanwhile, FindMySLQ *is* used by Calligra's cmake files. Akonadi might actually not be using libraries from the SQL port, but only the executable?

[NicosPavlov]

Thinking more about it, I realised this would not be a suitable approach, as ports still need to specifically indicate which SQL port they are using, typically through variants. Therefore, just introducing all the paths would not fulfil that goal.

A good example of what can be done is in fact provided in the amarok port, which uses its own local patched FindMySQL script, where variants indicate which SQL port is to be used. A similar approach might be the best for Calligra too.

[RJVB (René Bertin)]

This depends on whether it is supposed to be possible to install different sql ports.