https://bugzilla.redhat.com/show_bug.cgi?id=1482202 Tom Gundersen <tgunders@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tgunders@redhat.c | |om) | --- Comment #4 from Tom Gundersen <tgunders@xxxxxxxxxx> --- I will address the suggested changes for the spec file and push a new one in a minute. This answers the additional questions: dbus-broker is the core of the package, which is performance critical, and which should not have many dependencies (as it might be integrated into PID1 in the future). dbus-broker-launch on the other hand is just a wrapper that makes dbus-broker behave like dbus-daemon. It is not performance critical (only does config parsing at boot, but not really anything at runtime), this depends on libsystemd and glib. In the future we could split that into a separate package in case people start integrating dbus-broker directly and don't want the dependencies. Unlike the other libraries, c-sundry is just a collection of trivial but useful helpers that is not really meant to be released or ever shipped as a proper library (tagging it in git was a mistake, will drop that again). It makes more sense to just copy the needed bits into whatever project needs them. For us, we simply use git submodules, or in this case, depend on a specific commit. The alternative would be to copy the sources over, but that seemed unnecessary. Some of the libraries (but not all) only have inlined functions so far, but we took care that the pkg-config file can be used later to actually make them shared libraries, if necessary. So we just happen to not have any code in the shared lib, yet. But we are forward compatible to adding such. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
