It will not fail to compile. However, it appears that networkmanager uses dbus to communicate with dnsmasq. Furthermore, for the clients to succesfully associate, dhcp is apparently required. Reproducible: Always
Affirmative, dnsmasq uses these in its configure; so, if you happen to have the USE flags set differently in package.use you get inconsistent behavior. Assigned to maintaining herd.
dhcp? won't work as networkmanager doesn't have that USE, it has one for each provider :/
networkmanager always launches /usr/sbin/dnsmasq with --dhcp-range and --dhcp-option flags, so there is a hard dependency on dnsmasq[dhcp] that we were missing. However, as far as I can see, networkmanager does not use dnsmasq's dbus interface. You can easily check this: dnsmasq's dbus name is uk.org.thekelleys.dnsmasq, and the string "thekelleys" does not occur anywhere in networkmanager's source code. + 01 Oct 2013; Alexandre Rostovtsev <tetromino@gentoo.org> + networkmanager-0.9.6.4.ebuild, networkmanager-0.9.6.4-r1.ebuild, + networkmanager-0.9.8.2-r3.ebuild, networkmanager-0.9.8.4.ebuild: + Depend on dnsmasq[dhcp] for connection sharing (bug #475760, thanks to + Ronald).
