[debian-mysql] Common mechanism for detecting which MySQL variant and version is installed

Robie Basak robie.basak at ubuntu.com
Fri May 12 11:23:42 UTC 2017

Hi Ondřej,

On Fri, May 12, 2017 at 12:36:40PM +0200, Ondřej Surý wrote:
> as all packages depend on mysql-common, right? So we can include such
> script into
> the package and each *-server-core would then provide same magic file.

That would be fine I think. But is there any point in having a separate
script? If we agree on the format, then a script that just does "echo
<whatever>" could trivially be added to *-server-core without any need
to touch mysql-common.

> Also thinking in a long term - in theory we might be able to make
> *-*-core-* packages coinstallable with each other, so perhaps we need to
> think about this before crafting a solution. What do you think?

I think the problem we're trying to solve is to answer the question
"what is /usr/sbin/mysqld?" since that's what other build scripts are
calling but the parameters change depending on whether it is MySQL or
MariaDB. This may apply to some other executables as well, such as

Perhaps this is an indication that MariaDB packaging should be using
/usr/sbin/mariadbd or similar now, as their CLIs have now diverged. But
that's a separate discussion.

If we do end up with *-*-core-* packages being coinstallable, then I
don't think we'd have this problem to solve any more. The binaries would
have different paths and then maintainer scripts could easily change
behaviour based on the name they call.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170512/191eeed3/attachment.sig>

More information about the pkg-mysql-maint mailing list