On 2016-10-29 11:17, Arkadiusz Miśkiewicz wrote: > On Saturday 29 of October 2016, Elan Ruusamäe wrote: >> On 29.10.2016 11:25, Elan Ruusamäe wrote: >>> should we introduce mysql57, mysql80 packages instead? > > Only if there are incompatible on upgrade path. To be verified with docs. > Otherwise all versions as mysql package.
That (nameXY) would be more usefull for PostgreSQL, where old and new version need to be installed for a database upgrade between different major versions. Currently PostgreSQL upgrade in PLD is a problem. Though, I am not sure doing it right and maintaining later is worth the effort for our tiny team. >> here's some idea: >> >> 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6 >> 2. do not build mysql.spec officially at all >> 3. build system tools using percona-server-devel via "Provides: >> mysql-devel" 4. mariadb - ship it only if it does not conflict with >> mysql-libs or mysql-devel > > Sounds good to me. > > (I would switch entire distribution to mariadb though (but keep percona > server > package, too) Sound goot to me to. It seems other distributions do similarily – mariadb is used instead of Oracle mysql and no non-Oracle mysql fork is packaged as 'mysql'. Jacek _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en