| Summary: | sys-devel/distcc[avahi] init script needs to depend on dbus for zeroconf | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Luke-Jr <luke-jr+gentoobugs> |
| Component: | [OLD] Core system | Assignee: | Gentoo Cluster Team <cluster> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | cluster |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Luke-Jr
2011-11-30 20:58:21 UTC
It's not that distcc relies directly on dbus. Rather avahi relies on dbus and distcc relies on avahi for zeroconf support. Since the avahi-daemon service already requires the dbus service to start before avahi, the distccd daemon script should ensure that avahi is loaded - not dbus since avahi-daemon takes care of that.
The distccd init script currently contains the code
depend() {
need net
use avahi-daemon ypbind
}
The text "use avahi-daemon ypbind" can just be deleted if the avahi use flag is off. If the avahi use flag is on, the script can be changed to "need net avahi-daemon". I really have no idea why ypbind is mentioned. Unless someone else knows something I don't, I don't think this is necessary or useful.
|