-
- Downloads
daemon: Remove org.apertis.Sensors1 well-known D-Bus name
While in principle it’s a good idea to have a non-project-specific generic well-known name to expose services on, this only makes sense if the object paths, interface names and other naming are also generic, which they are not for Rhosydd. Since Rhosydd is (for the foreseeable future) likely to be the only sensors and actuators daemon on the system, it’s safe to simply use org.apertis.Rhosydd1 as //the// well-known name for the SDK sensors API. As the vehicle manager interface has now been removed, which is what was exposed to backends, there is also no need to keep two sets of objects exposed separately by the daemon. Reviewed-by:Simon McVittie <simon.mcvittie@collabora.co.uk> Signed-off-by:
Philip Withnall <philip.withnall@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D3156
Showing
- Makefile.am 0 additions, 1 deletionMakefile.am
- daemon/org.apertis.Rhosydd1.conf.in 2 additions, 3 deletionsdaemon/org.apertis.Rhosydd1.conf.in
- daemon/org.apertis.Sensors1.service.in 0 additions, 5 deletionsdaemon/org.apertis.Sensors1.service.in
- daemon/service.c 0 additions, 32 deletionsdaemon/service.c
- daemon/usr.bin.rhosydd 0 additions, 6 deletionsdaemon/usr.bin.rhosydd
- debian/rhosydd.install 0 additions, 1 deletiondebian/rhosydd.install
- librhosydd/vehicle-manager.c 3 additions, 3 deletionslibrhosydd/vehicle-manager.c
- tests/integration.py 1 addition, 1 deletiontests/integration.py
Loading
Please register or sign in to comment