Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Sebastien FLAESCH
On 05/17/2013 03:07 PM, Reindl Harald wrote: Am 17.05.2013 14:53, schrieb Sebastien FLAESCH: On 05/17/2013 12:29 PM, Reindl Harald wrote: Am 17.05.2013 12:05, schrieb Sebastien FLAESCH: Beside the Oracle skills debate and the stupid mistakes with soname changes between 5.5.8 and 5.5.10 or

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Reindl Harald
Am 17.05.2013 14:53, schrieb Sebastien FLAESCH: > On 05/17/2013 12:29 PM, Reindl Harald wrote: >> >> >> Am 17.05.2013 12:05, schrieb Sebastien FLAESCH: >>> Beside the Oracle skills debate and the stupid mistakes with soname >>> changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did >

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Sebastien FLAESCH
On 05/17/2013 12:29 PM, Reindl Harald wrote: Am 17.05.2013 12:05, schrieb Sebastien FLAESCH: Beside the Oracle skills debate and the stupid mistakes with soname changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did not happen): I have a VERY simple question that needs a VERY CLE

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Reindl Harald
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH: > Beside the Oracle skills debate and the stupid mistakes with soname > changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did > not happen): > > I have a VERY simple question that needs a VERY CLEAR answer: > > In our distribution pa

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Sebastien FLAESCH
Beside the Oracle skills debate and the stupid mistakes with soname changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did not happen): I have a VERY simple question that needs a VERY CLEAR answer: In our distribution packages (for different platforms! not only Linux), I need to pro

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Reindl Harald
Oracle fails the context by make incompatible ABI changes which are *expected* by raise the minor release number but claim they are compatible until it is clear that random things are broken and the soname needs to be changed what leaves the question: was the QA at holiday due the whole development

Re: MySQL Client (libmysqlclient) compatibility policy

2013-05-17 Thread Sebastien FLAESCH
Hi all, Could someone from the libmysqlclient contributors comment on this, and could someone complete the documentation regarding client compatiblity? Thanks! Seb On 02/20/2013 09:31 AM, Sebastien FLAESCH wrote: Hello, FYI, I found this statement in the doc, at the end of the C API main page