Should MariaDB touch my.cnf in %post?

["Jóhann B. Guðmundsson"]

On 02/15/2013 11:07 AM, Honza Horak wrote:
> 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.

How so?

If fesco does not ban mysql from the distribution then upgrades should 
not be painful because you would simply upgrade to the latest mysql 
release in the distribution.

If mysql on the other hand is banned in the distribution then arguably 
it makes sense to migrate those instances to the latest release of 
mariadb instead thou I personally would not recommended it then either 
but rather prefer it would be left alone then replaced by admin himself 
after upgrade.

<snip>
> 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?
>

Different product different characteristics

>> 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.

Same fundamental rules apply as I see it just different ( fork ) components.

>
>> 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.

Is that not an clear indicator that the replacement should not take 
place on upgrade but rather be left up to the administrator to do 
manually ( at least while we still ship mysql ) and we have mysql and 
mariadb conflict with each other on packaging level?

JBG