[debian-mysql] Managing switches between *-{server|client}-{core|}-x.x variants

James Page james.page at ubuntu.com
Sat Mar 1 15:37:20 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Team

Managing the Breaks/Replaces/Conflicts between the (nearly) four mysql
options with have across unstable and experimental needs to get a bit
more intelligent; I had a play around with mysql-5.5, mysql-5.6 and
mariadb-5.5 today and here is what I propose:

1) we manage all file conflicts with Breaks/Replaces - this avoids the
hardness of Conflicts which as we have discuss in ML and in irc before
could be an issue during upgrades

2) each level of binary package declares an appropriate Provides, e.g.

mysql-client-core-5.5,mysql-client-core-5.6,mariadb-client-core-5.6:
 	Provides: virtual-mysql-client-core

mysql-client-5.5,mysql-client-5.6,mariadb-client-5.6:
 	Provides: virtual-mysql-client

etc...

3) each binary package also Breaks/Replaces its Provides:

mysql-client-5.5,mysql-client-5.6,mariadb-client-5.6:

Breaks: virtual-mysql-client
Replaces: virtual-mysql-client
Provides: virtual-mysql-client

in the example above, as each *-client-X.X package does the same
thing, they should just switch in/out OK.

4) upgrades from previous releases

We will need to leave in some Breaks/Replaces - to deal with upgrades
from the mysql-5.5 version currently in stable as these won't provide
all of the virtual-* stuff.

Thoughts?

If this makes sense to folk I'll take some time to apply and test this
in full with the three variant we have in archive today.

Cheers

James


James Page
Ubuntu and Debian Developer
james.page at ubuntu.com
jamespage at debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTEf6wAAoJEL/srsug59jDMdsP/3K8o5UgdZ8gXSrE/Elay06k
KOLVeYJ2fqMymfaul7xxzVkcJTbcDwvnqsoPxRsM1erHLlpahy4vyxa3ftjwlIDy
DTGRu2NAfwt4qOxgmNwoMPzpC5eEwLum7gsUCPRVi/69h/gfxtDgyB9Diy/QmOsA
6b35cmywewloLhouskgTOu9oZTsSFeo1QYA+72MFUYEYl3UFJxaYGI6Q0jgJ175y
rCWNDY+ed0wJlqNLPbNXGSeTtT1fRst5N3Ac18r3k5o4WvY64BEhfTolpH5aZ9MC
DCQY7v3RUxTFrCEHJGz0Ft6vujSrFjfSWq6xpfJpFRkoSVLMMDH2ywVL9lauS0JQ
zUzGaNkphf/W8mLUU8w46fi8I15HWps6kfkiKXrf+Kwpzah7pR5q2q/7VGUYVldu
Z+K5Bj/zYwObwBrY+Rf+y/TDGaJJH4r3HoO6anCxMye7BYsghVbUXjF39x03d/Ib
dTX9dbHTerymO/qlriwSnSE2rb6vWa/acSb55luppsunSRu9HpQvjukhZzHsGksF
f+l3NW0AZPF3XDgBEH5wY9s+AxaqPXpGi67YcGde30zRn/ZMZKG981Oc00Fx9bH0
K8VmJSu1BgaccOFry9JMq5cJd0ttMiAHT00bfDf4DFoZOSXORX3eYE1z0gTOes9f
4KntYrpexrZ/Jp2Yp8Kf
=nvVE
-----END PGP SIGNATURE-----



More information about the pkg-mysql-maint mailing list