[debian-mysql] Backporting MySQL?

[Dominic Hargreaves]

On Fri, Jun 24, 2016 at 09:02:46AM -0700, Clint Byrum wrote:
> Excerpts from Dominic Hargreaves's message of 2016-06-24 16:50:58 +0100:
> > On Fri, Jun 24, 2016 at 07:35:47AM -0700, Clint Byrum wrote:
> > > Excerpts from Dominic Hargreaves's message of 2016-06-24 15:27:17 +0100:
> > > > Hi,
> > > > 
> > > > We have a requirement to use MySQL 5.6 on our jessie system, and 
> > > > happily the local backport was trivial (no source changes were required)
> > > > and works fine in our testing. It'd be great to have this available in
> > > > the official backports repo so that others can benefit too.
> > > > 
> > > > Would people be happy for me to upload a backport of 5.6.30-1
> > > > (as of now) to jessie-backports, or would the MySQL maintainers prefer
> > > > to be involved directly?
> > > 
> > > Can I assume you removed libmysqlclient/client programs/etc. from the
> > > build?
> > > 
> > > Perhaps you could post a link to the source tree or dsc's so we can diff
> > > for ourselves.
> > 
> > No, as per the above I didn't make any source changes. I can only asssume
> > that you think they should be removed for some reason; could you say why?
> 
> Hrm, I guess I was thinking we wouldn't want users to update their
> libmysqlclient18 from a new major version. But in re-reading the
> backports rules page [1] I see that I am just projecting Ubuntu
> Backports rules onto Debian backports.
> 
> Perhaps somebody else more experienced with Debian backports can confirm
> that it would be ok to include a newer libmysqlclient18.

I don't see why it wouldn't. There are many shared libraries already
in the backports. Of course it would be different if the ABI changed,
but that's not the case here.

Dominic.