MER: Add packaging.
MER: Remove plugin descriptors

We don't want these in the -devel package, because the devel package does not
install everything.
Support logging direct to journald, if enabled.

Instead of merely intercepting logging output from stdout/stderr from the
journal side of started processes, this has the advantage of meaning that the
origin process name will be correct.

fprintf won't work, because if a process starts children (like e.g. a
homescreen does), then their stdout/stderr are merged into their parent, and
journal has no way of differentiating the origin.

We are also able to store information about the context of logging, which might
be useful in post-mortem cases.

[ChangeLog][Platform Specific Changes][Linux] Systems with systemd may now pass
-journald to configure to send logging output to journald. Logging will still be
sent to stderr for interactive applications (run from a tty) or with
QT_NO_JOURNALD_LOG set to a non-empty value.

Change-Id: Ib260cec1ea87390bf44f267d217d795583407d00
Support discovery of key evdev devices.

Change-Id: Iac2751b51fb0af9fba181c26ad788f25eb0b02f7
Done-with: Andrew den Exter <andrew.den.exter@jollamobile.com>
EvdevTouch: Don't remove released touch data for Type B; only ignore slot

The Type B protocol states that touch slots with an ID of -1 should be
considered unused, but data should be retained if that slot becomes
active again later. Instead of removing the contact from the contact list,
only "disable" it. This contact can later be reused if the slot becomes
active again.

Change-Id: I827ae311841dd97f73a2c64d943658cd3f29eaf8
Done-with: Andrew Knight <andrew.knight@digia.com>
evdevtouch: Don't try to keep reading on EAGAIN

This stops touching the screen (and not moving) consuming 80-90% CPU.
The mtdev and non-mtdev codepaths have been separated for additional clarity.

Change-Id: I0559a6bd80dab961fdb4a83ad50860a9aec6445c
Increment loopLevel prior to emitting aboutToBlock()/awake() signals

Without this, any deferred delete actions that occur as a result of
these signals will not be processed until the main event loop exits.

This is triggered by the QtWayland server, which uses aboutToBlock() to
process internal events such as surface destruction.

This is most likely a problem with other dispatcher instances, but the scope of
this change cannot be to fix every platform at once, so the test is deliberately
marked QEXPECT_FAIL for everything except the glib dispatcher for now.

Done-with: Aaron Kennedy <aaron.kennedy@jollamobile.com>
Task-number: QTBUG-36434
Change-Id: I3fc143ad442c3a499d09f795355c155ad21b126d