maria-developers team mailing list archive

[darx@xxxxxxxx]

Hi,

I've a custom my.cnf

	ls -al /usr/local/etc/mariadb/my.cnf
		-rw-r--r--+ 1 root root 7.9K Jul 13 13:03
		/usr/local/etc/mariadb/my.cnf

If I (re)install mariadb 10/trunk from a src build with SYSCONFDIR
spec'd for that dir, as done similarly to a MySQL build,

	cd mariadb/bld
	cmake .. \
	 ...
	 -DINSTALL_SYSCONFDIR=/usr/local/etc/mariadb \
	 ...
	make
	make install

The INSTALL process *destructively* overwrites the existing my.cnf

	...
	-- Up-to-date: /usr/local/etc/mariadb/logrotate.d/mysql
	-- Up-to-date: /usr/local/etc/mariadb/init.d/mysql
	-- Installing: /usr/local/etc/mariadb/my.cnf     
	<================================ !!
	-- Up-to-date: /usr/local/etc/mariadb/my.cnf.d/client.cnf
	-- Up-to-date: /usr/local/etc/mariadb/my.cnf.d/mysql-clients.cnf
	-- Up-to-date: /usr/local/etc/mariadb/my.cnf.d/server.cnf
	...

with an older default cnf,

	ls -al /usr/local/etc/mariadb/my.cnf
		-rw-r--r--+ 1 root root 202 Jul 12 11:31
		/usr/local/etc/mariadb/my.cnf

with no backup made of the existing cnf,

	find /usr/local/etc/mariadb -type f -name 'my.cnf*'
		/usr/local/etc/mariadb/my.cnf

This is critically different behavior that MySQL.

If that's intended, how are we to exec a mariadb install without
overwriting our config files/dirs?

If it's not, I suspect this should be fixed.

Thanks.