Bug#702280: Add alternative (build-)dependency: libmariadbclient-dev

[Otto Kekäläinen]

Hello,

2013/3/4 gregor herrmann <gregoa at debian.org>:
> [..]
>> What is the correct way to insert "libmariadbclient18 (>= 5.5.1-1) |
>> libmysqlclient18 (>= 5.5.1-1)" in there?
>
> That's only possbile with more or less ugly hacks from the
> libdbd-mysql-perl side.

I tried building the package with debian/control for the binary
package like this:
Depends: libmariadbclient18 (>= 5.5.13-1) | libmysqlclient18 (>=
5.5.13-1), ${misc:Depends}, ${shlibs:Depends}, ${perl:Depends},
 libdbi-perl (>= 1.610.90)

But the end result is somehow still:
Depends: libmysqlclient18 (>= 5.5.13-1), libc6 (>= 2.4), perl (>=
5.14.2-6ubuntu2.2), perl-dbdabi-94, perlapi-5.14.2, libdbi-perl (>=
1.610.90)

So apparently some special tricks are required, as you wrote.

> But as Rene has already pointed out, changing Build-Depends to
> "libmariadbclient-dev | libmysqlclient-dev" makes the package
> immediately unbuildable and therefore RC-buggy if
> libmariadbclient-dev is not yet in the archive.

Yes, I understood that my original suggestion to change the
Build-Depends is bad in several ways. We should not insert
libmariadbclient-dev at this point at all.

Ideas on how to nicely control the binary package dependency? What
would the "ugly hack" be? Can it in any way be made somehow more
elegant? :)

> (Besides that, any such major changed will have to wait until after
> the wheezy release.)

Ok, we can postpone the upload but could we now try to figure out the
technical solution of what will be eventually uploaded?


Thanks for your help and quick replies to my bug report today!

- Otto