In version 3.27 and 3.28 some parts of the package have been made optional and need to be enabled by configure options. They are dund, tools, and expat. This means that dund is not being installed. Possibly some other things too. Reproducible: Always Steps to Reproduce: 1.emerge bluez-utils 2. 3. Actual Results: dund, and possibly other utilities, not compiled as they need to be enabled by configure options Expected Results: Installed dund as part of the package. Perhaps it would be best to have the new options as USE flags.
USE="old-daemons"
Either you're not using version 3.27 or later or your dund actually comes from somewhere else. The old-daemons USE flag only enables the options sdpd, hidd, and pand. It does not enable dund. # USE="old-daemons" emerge bluez-utils ... # dund -su: /usr/bin/dund: No such file or directory # hash -r # dund -su: dund: command not found
(In reply to comment #2) > Either you're not using version 3.27 or later or your dund actually comes from > somewhere else. The old-daemons USE flag only enables the options sdpd, hidd, > and pand. It does not enable dund. > Well people should use the service apis any way.
*** Bug 213735 has been marked as a duplicate of this bug. ***
Bluez-utils-3.30 can easily be made to include dund (which I've been experimenting with recently for use with gnubox). It's missing the following line (even though many other old-daemon tools seem to have a relevant line): $(use_enable old-daemons dund) \ I'd much prefer to use the new network architecture, though. Betelgeuse, do you know how to replicate the dund functionality using the new services? I've been using d-feet to enable the /org/bluez/network/nap device, but I'm not sure what that actually does? It doesn't seem to create a pan1 interface, and I'm not certain how then to interface that with pppd even if it did? I've read the network-api.txt and the wiki pages on networking, but they don't contain a great deal of information on creating dial-up networking solutions. Dund seems to do it all for me, so it might be worth adding this extra line in anyway, until the new services are better understood/have better documentation...
*** Bug 216122 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > Bluez-utils-3.30 can easily be made to include dund (which I've been > experimenting with recently for use with gnubox). It's missing the following > line (even though many other old-daemon tools seem to have a relevant line): > > $(use_enable old-daemons dund) \ > What it means the last line? I must emerge bluez-utils with this use flag?or other?
Ok, dund gets built with USE="old-daemons", expat isn't there anymore around in 3.36 , tools get always built. I'd guess that building tools always is a good idea.
ok, I guess we can close this now as fixed since 3.36 gets stable.
