dbus-triggerd, a helpful little daemon

dbus-triggerd is a little daemon that can monitor dbus events, match them against some watch-expressions, then trigger shell-commands.

It can be used in any situation where dbus-interaction is needed, and shell script is preferred over other languages.

Signed-off-by Arnaud R?billout <[email protected]>

---
 package/Config.in                                  |  1 +
 package/dbus-triggerd/Config.in                    |  9 ++++++++
 .../dbus-triggerd-01-cross-compil.patch            | 13 ++++++++++++
 package/dbus-triggerd/dbus-triggerd.mk             | 24 ++++++++++++++++++++++
 4 files changed, 47 insertions(+)
 create mode 100644 package/dbus-triggerd/Config.in
 create mode 100644 package/dbus-triggerd/dbus-triggerd-01-cross-compil.patch
 create mode 100644 package/dbus-triggerd/dbus-triggerd.mk

package/Config.in +1 -0

index cfa53d3..fa24b57 100644
@@ -272,6 +272,7 @@ source "package/dbus/Config.in"
 source "package/dbus-cpp/Config.in"
 source "package/dbus-glib/Config.in"
 source "package/dbus-python/Config.in"
+source "package/dbus-triggerd/Config.in"
 if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
 source "package/devmem2/Config.in"
 endif

package/dbus-triggerd/Config.in new file +0 -0

new file mode 100644
index 0000000..e7f65b8

package/dbus-triggerd/dbus-triggerd-01-cross-compil.patch new file +3 -0

+ 
+ all: dbus-triggerd
+ 

package/dbus-triggerd/dbus-triggerd.mk new file +6 -0

new file mode 100644
index 0000000..fa04c06
@@ -0,0 +1,24 @@
+################################################################################
+#
+# dbus-triggerd
+#
+################################################################################
+

package/dbus-triggerd/dbus-triggerd.mk new file +8 -0

+	$(MAKE) -C $(@D) all
+endef
+
+define DBUS_TRIGGERD_INSTALL_TARGET_CMDS
+	$(MAKE) DESTDIR="$(TARGET_DIR)" -C $(@D) install
+endef
+
+$(eval $(generic-package))

For the other dbus-* packages, the dbus dependencies are repeated (even
though they're automatic because of the depends on DBUS). So I would do that here as well. And that means of course that there should also be a comment in case of missing toolchain features. See dbus-cpp for an example.

Patch misses a description + Signed-off-by.

If you're anyway patching the Makefile, you can just as well make it:

CFLAGS?=-Wall -O3
CFLAGS+=$(PKG_CONFIG) --cflags dbus-1
LDLIBS+=$(PKG_CONFIG) --libs dbus-1

Will you send this patch upstream?

This should be $(TARGET_CONFIGURE_OPTS) which includes all of the above
and more.

Note BTW that the patch above refers to LDLIBS instead of LDFLAGS. Is
LDFLAGS used?

Hi Arnout,

Quoted 4 lines

For the other dbus-* packages, the dbus dependencies are repeated (even
though they're automatic because of the depends on DBUS). So I would do that here as well. And that means of course that there should also be a comment in case of missing toolchain features. See dbus-cpp for an example.

You're right, I forgot the comments, and the host-pkgconf dependency as well. I will do as you suggest for the DBUS dependencies.

Quoted 1 line

Patch misses a description + Signed-off-by.

Correct.

Quoted 8 lines

If you're anyway patching the Makefile, you can just as well make it:

CFLAGS?=-Wall -O3
CFLAGS+=$(PKG_CONFIG) --cflags dbus-1
LDLIBS+=$(PKG_CONFIG) --libs dbus-1

Quoted 1 line

Will you send this patch upstream?

Yep. I will send a patch right now.

Quoted 2 lines

This should be $(TARGET_CONFIGURE_OPTS) which includes all of the above
and more.

OK. Actually, I've always been wondering it was OK to use TARGET_CONFIGURE_OPTS in a generic package, I never dared to do it.

Quoted 3 lines

Note BTW that the patch above refers to LDLIBS instead of LDFLAGS. Is
LDFLAGS used?

Yep, LDFLAGS is used automatically by Make in this Makefile.

Thanks for your comments, I will send the patch upstream a wait a little for the author's comments on it.

Regards

Signature · 1 line

Arnaud R?billout