mga: SPEC file, from Mageia
mga: gitify the spec file
PostgreSQL: respect port setting for db connection

We may be using a different port than 5432, send that to QSqlDatabase.
server/connection.cpp: try to release idle connections to DB

For Postgres, each DB client connection corresponds to a process
being spawn and kept alive. May even mean some SHM allocated for
it, on pre-9.3 versions of postgres.
On a system (desktop) with many akonadi resources, we may end up
occupying most/all available Postgres backends just keeping idle
agents.
This patch tries to address that, by releasing the DB connection
for those idle agents. This comes to the expense of some wake-up
latency (connect, setup db and prepare queries again). It is not
limited to QPSQL DBs yet, as to explore its effects on the other
storage engines.

Note that I had to change the `DataStore::database()` API from a
const to a regular method, because it would wake-up a connection.

With the help of Daniel Vrátil <dvratil@redhat.com> , who showed
me the way.
datastore: initialize db stores in closed db state

As a PoC to the db-connections-release feature, I start all datastores
in non-open state, now. They will lazily be connected a bit later, as
soon as the first query is requested (guarranteed to happen, anyway).
connection: reduce db-release timeout to 3min

Playing around with timings, now that the feature seems stable.
dbconfig,connection: make db-release timer configurable

Now, the default will again be /not/ to close idle backend connections.
But, with a setting like:

  [%General]
  Driver=QPSQL
  ConnectionIdleSecs=180

.. the feature will be activated and set to 3min, eg.

This is a slight API change, backwards compatible.
connection,db-postgres: remove debug statements
connection,datastore: remove overly variable clearers
datastore: always use brackets at conditionals
connection: protect slotConnectionIdle against running in transaction

Assert that there is no active handler (meaning in middle of a query),
but also gently avoid closing if DB connection is at a transaction.
connection: make sure we check DataStore with "m_backend" initialized