Should MariaDB touch my.cnf in %post?

[Honza Horak]

On 02/15/2013 11:27 AM, "Jóhann B. Guðmundsson" wrote:
> Mariadb is evolving into it's own product with it's own feature set [1]
> thus should be treated as different product it should have it's own .cnf
> file it's own configuration directory which is best in the long run (
> from my pov ).

Then it should also need separate binaries, libraries, datadir, socket, 
... I'm not saying it is so bad idea, but it could be taken into account 
only in the upstream, we really cannot do something like that 
downstream. And we'd probably lost the drop-in feature and upgrade would 
be even more painful.

> If I install a component what ever component I then upgrade I expect
> that a) I get the latest and the greatest release of that component b)
> still be running the same release of the component if not newer release
> is found or if the component is no longer being shipped.
>
> I dont expect a) that the component gets removed on upgrade, b) that I
> magically somehow get migrated to a different product.
>
> Let me take other examples of what I'm trying to refer to here with
> regards to expected behavior.
>
> If you would install libreoffice would you expect to be running
> openoffice after upgrade or would you expect to be starting libreoffice
> after the upgrade?

In case it would be discussed, compatible, documented, noted in the 
release notes and we have a good reason to do so -- then why not?

> If you install mate or cinnamon or unity for that matter would you
> expect to be migrated and running Gnome 3.x after upgrade or would you
> expect to be continuing to use and run what got forked or based of it.

This is already too extreme, we cannot compare Gnome forks and MySQL 
forks. It's really a different scenario.

> One usage scenario one simple question
>
> If an user wants to run both those database solution on his server wont
> those two overlap as in can for exaxmple users be asssured that the
> changes that they make to their my.cnf wont get picked up by mariadb
> when it gets started etc.

Running both packages on the same server is not currently available, 
because they conflict. If somebody does it in any way, which means to 
separate files, sockets, ... then he should be able to separate config 
files as well.

Honza