Robie,
I have no idea why are you talking about -compat packages and mariadb
shipping libmysqlclient.
The initial email stated:
> Packages built against default-mysqlclient-dev and link using
> "-lmysqlclient" will end up with a shared library dependency on either
> libmysqlclient.so.X or
On Tue, Sep 06, 2016 at 09:00:37AM +0200, Ondřej Surý wrote:
> So again I urge you to revert the decision to introduce yet another
> change in the Build-Depends for >= 300 packages and just use the
> libmysqlclient-dev package to be the "default".
Sorry, I disagree. The situation with MariaDB
Robie,
there's exactly similar situation with libjpeg62. There's a default
libjpeg-dev package that depends on libjpeg62-turbo-dev
ondrej@yugen:~$ apt-file show libjpeg62-turbo
libjpeg62-turbo: /usr/lib/x86_64-linux-gnu/libjpeg.so.62
libjpeg62-turbo: /usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
Excerpts from Robie Basak's message of 2016-09-05 18:59:39 +0100:
> Hi Ondřej,
>
> On Mon, Sep 05, 2016 at 08:57:57AM +0200, Ondřej Surý wrote:
> > could you elaborate a bit more why you are forcing all Build-RDeps to
> > change B-D to default-libmysqlclient-dev instead of just changing the
> >
Hi Ondřej,
On Mon, Sep 05, 2016 at 08:57:57AM +0200, Ondřej Surý wrote:
> could you elaborate a bit more why you are forcing all Build-RDeps to
> change B-D to default-libmysqlclient-dev instead of just changing the
> semantics of libmysqlclient-dev?
MySQL ships the soname libmysqlclient.so.20
Hi,
On Tue, Aug 16, 2016 at 11:36:15AM +0300, Otto Kekäläinen wrote:
> Yes, this scheme is very flexible and in cases like
> > mysql-connector-c++ the package can depend explicitly on the MySQL
> > package and not the default package.
OK.
> > Or we keep a
Hello!
2016-08-16 7:44 GMT+03:00 Rene Engelhard :
> On Sun, Jul 10, 2016 at 05:22:22PM +0300, Otto Kekäläinen wrote:
>> Hello maintainers of packages that depend in MySQL/MariaDB!
>
> Not everyone is required to read -devel. Mailing them where they read
> it (and be it Cc'ing
7 matches
Mail list logo