On Sat, Mar 08, 2014 at 11:17:01AM +0000, Mark Shuttleworth wrote: > > To my mind the current proposal is no more than saying "mysql-5.6 will > be available in a separate archive". The proposal uses Universe the way > it should be used - the code is available, and packaged, but for > whatever reason we don't currently want it in main. It does leave open > the option, however, for us to make the same commitment to it as full > maintenance, later on, if it turns out that "customers DO want it!" :) > So I would be supportive of the more open-ended approach in universe.
For mysql, it's a bit stickier than for OpenStack. The latter is, largely, a bunch of python modules and the like, all of which are just new versions of the same packages. The biggest issue is the client library version, which is linked in to a mess of stuff, and one needs to be very careful when having two around to make sure things are sane. Speaking of sane, the thing that claims to be libmysqlclient18.1 from mysql-5.6 actually has an SONAME of libmysqlclient.so.18 according to the ELF headers. Not sure which packager thought that adding a link from libmysqlclient.so.18.1 somehow magically made it not be .18, but they're wrong. As it stands, the client libs from mysql5.5 and mysql5.6 should not be coinstallable (even though they are), so that would need to be fixed. And fixing that would mean promoting 5.6 to main, since it would now provide the current version of the client lib. ... Adam -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
