Should MariaDB touch my.cnf in %post?

[Reindl Harald]

Am 12.02.2013 18:46, schrieb Honza Horak:
> I'd like to share an idea related to MySQL->MariaDB move, that may be a bit controversial. Speaking about default
> case in Fedora, MySQL has used only one file at /etc/my.cnf to configure server, libraries, command-line utilities,
> etc.
> 
> MariaDB uses by default /etc/my.cnf and /etc/my.cnf.d/{client,server,..}.cnf files, while all the /etc/my.cnf.d
> directory is included using !includedir statement in /etc/my.cnf.
> 
> The problem is, that after replacing MySQL with MariaDB existed my.cnf won't get updated (uses
> "%config(noreplace)") and then users will be confused by having /etc/my.cnf.d/* files, which won't be used.
> 
> A solution proposed by MariaDB upstream would be adding !includedir directive into /etc/my.cnf (if not already
> done) in mariadb's %post section. That would mean *modifying user's configuration during RPM update*.
> 
> I haven't found any restriction forbidding this solution, but would like to collect opinions, how bad it is,
> because we're aware it's not very clean -- however, it has it's benefits.
> 
> In case user won't wish to use !includedir anymore, he'd comment it out and it won't get added again.

please do not touch /etc/my.cnf

any real used mysqld will have a customized /etc/my.cnf and no admin
should do this migartion without take really care what happens and
test this before - unclean soltutions will hurt sooner or later
in moments where this is not expected

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130212/36e61e3c/attachment.sig>