Comment 6 for bug 673844

I completely agree with the other posts here.
Expected behavior of any shipped package which requires a configuration file is to provide a default template configuration.
MySQL distributions have ALWAYS done this, and I can see zero good reason to change this.

Expected result of including a default configuration:
  People who aren't DBAs but willing to start out slow will be able to get going quickly.
  People who are DBAs will not care.

Expected result of not including a default configuration:
  For people installing Percona 5.5 the first time (eg, me, who has years of MySQL/Percona experience) now has to sit here and hand craft a new configuration for what was supposed to be a trivial use case and only needed a very basic MySQL install (one where I could tweak the config later but I needed to not care about the DB for now).

The moment I saw the configuration file wasn't there, I installed PostgreSQL. Extreme reaction? maybe. But PostgreSQL was up and running in under 2 minutes. That's what I care about. You've made it too difficult now, for the many people who don't want to worry about their database.

It's EASY to include sane defaults which minimally work and at least let people get started.
Even the stock MySQL 5.5 package for Ubuntu can seem to manage this. Please reconsider this decision.
Not everyone is a DBA, and not everyone has time to build a configuration file from scratch.