GitLab

With this we should be sending correct arguments to logind depending on
the state we want to inhibit.

Now Shutdown will be poweroff and reboot as well and we will have a
specific job for this state as well.

It looks like this is a pattern that happens for all cases:
Screen: DPMS and Brightness
Shutdown: Reboot and Poweroff
Sleep: Hibernation, Suspend, Hybrid

The single responsability of this class is to create arguments valid for
logind Inhibit call.

It will tackle some peculiarities of logind like for example not being
able to inhibit only reboot o poweroff.

Until now the states were kinda inherited from the old solid code and we
stpend no time thinking wether they make any sense or not. Now that we
are about to implement them we need to make more sense.

Current states:
Sleep: Sets the device to the preferred sleep method (s2ram, s2disk..)
	It also allows to inhibit any sleep (s2ram, s2disk, hybrid...)
Screen: A set of jobs exits to modify the state of the screen
	(brightnessChange, PowerOffScreen, etc...)
	It allow to inhibit any actions on the screen (brightness,
        dimming, powering it off...)
Reboot: Can be used to reboot the device
	It also can be used to inhibit reboot
PowerOff: Can be used to poweroff the device
	It also can be used to inhibit poweroff

It might happen that the backend job is gone (since it will auto delete
after calling emitResult) but the frontend job is still alive. If that
happens and somebody calls isPLugged() we will be asking info from a
deleted pointer.

This patch adds a copy of the result (a bool) plus a isBackendFinished
status to know when the backend job has finished.

On both cases we want to properly stop the inhibition which in the case
of systemd it means closing the file descriptor we got via DBus.

Once the inhibitio is started we are no longer interested in any signals
from this object.

We have created a fakeLogind dbus daemon to do a component test of
InhibitionJob which emits a "newInhibition" signal when the dbus method
gets called.

Also, there is code prepared to return proper file descriptors and to
test the Inhibition object further, but that part is still not done.

At some point we will need a proper backend loading system, atm this
works just fine.

introduce 2 other states, Reboot and Poweroff

plus some docu additions

while getting acquainted with the code

This command will connect to all signals from Solid::Power and reprot
any change that is detected in the system.

It seems to be the easier way of sharing one.

Small tool that will be able to report anything related (and supported)
to power using Solid::Power.

At the moment it only implements Show which reports wether the ac is
plugged or not.

TODO for the tool is:
-Listen to events
-Implement all other commands.

We check that we are properly getting the
freedesktop.Properties.PropertiesChanged signal and that we are
extracting the value correclty from it.

We also emit it twice and make sure we get things right.

onBattery == true, means we are NOT on AC.

At some point we will make solid compile with QT_NO_CAST_* so
we better use these now.

As difference with the past, now we are introducing a freedesktop
backend rather than a "upower/udev/systemd/ separate backends. This
allows us to be more flexible and to make sure we support freedesktop
correctly.

This first import comes with component test that checks how we are
handling dbus and what dbus calls we are doing.

Add metadata about the QMake and CMake packages installed by this framework and remove Links from README.md

allowed by Bison special exception