Packaging Requirements for 2.0

[digitaltrails]

The release of vdu_controls 2.0, introduces some new optional, but recommended, packaging requirements.

I've written a new D-Bus ddcutil-service that delivers much faster access to DDC (via i2c-dev). The service runs continuously and eliminates the overheads of shell, exec, and ddcutil initialisation. This results in a snappier and smoother experience when using vdu_controls.

If packaging vdu_controls 2.0, also consider packaging ddcutil-service and adding it as a dependency for vdu_controls.

ddcutil-service has a dependency on libddcutil, part of ddcutil. I've tested ddcutil-service with ddcutil/libddcutil` version 1.4 and up. It may also work with earlier versions and I' prepared to assist with that if there is a need.

If ddcutil is already packaged, it's quite likely libddcutil is also packaged. The library is also dependency of ddcui, and possibly some newer KDE components.

On startup vdu_controls will attempt to contact ddcutil-service. If the service is unavailable, vdu_controls will fallback to using the ddcutil command. Whether to use the service or command can also be manually controlled by settings.