Comment 5 for bug 673844

Here I cannot find any clear explanation why my.cnf is not shipped by default. This means a clean installation of Percona is partially broken until manual intervention. Of course I know I have to check my configuration after installation, but that is not a valid argument for leaving a default configuration out. I also know there is no one-size-fits-all configuration, but this wasn't an issue in version 5.1. Moreover I think installation of Percona should be as close as possible like a standard MySQL installation, although I know Percona is not MySQL. This means that, in case a default configuration would only be applicable for 1% of the users, at least 1% can start working without any problem. Right now we have the situation of users shooting themselves in the foot not knowing they have to create their own configuration, which is not obvious for users new to Percona.

One more thing. I found out about the missing configuration when upgrading my Percona installation from 5.1 to 5.5 in my testing environment. Purging the old 5.1 installation files removed the my.cnf file. I have this habit of keeping my system clean and tidy (as every administrator should), and purge old not used packages. Purging maybe not the best practice, but it is only in this case of cross package dependency it is causing trouble.

Hope my considerations can help to improve your products.

(ps. I originally made this comment in question #186599)