Disclaimer: this bug has been filed in a semi-automated manner.
When emerging the package net-wireless/bluez-4.99, the following elog messages are displayed:
* If you want to use rfcomm as a normal user, you need to add the user
* to the uucp group.
* You will need to add bluetooth service to default runlevel
* for getting your devices detected from startup without needing
* to reconnect them. For that please run:
* 'rc-update add bluetooth default'
Such messages should only be displayed when the package is a new install.
These situations can be checked in the ebuild as follows:
if ! has_version 'net-wireless/bluez'; then
See the tracker bug 440214 for more details.
The service part should probably check if it has been added to a runlevel and just dropped if bluetooth is supposed to be auto-started when a bluetooth device is detected ?
I have no opinion on the user/group stuff.
Didn't bluez remove the udev rule file it shipped at upstream level and recommended using the init system again?
the part related with adding service to boot is already shown only when needed:
if [ "$(rc-config list default | grep bluetooth)" = "" ] ; then
elog "You will need to add bluetooth service to default runlevel"
elog "for getting your devices detected from startup without needing"
elog "to reconnect them. For that please run:"
elog "'rc-update add bluetooth default'"
Regarding the other message, it's inherited for a long time and I need some docs showing it's no longer needed (as I can't test it myself):
if use consolekit; then
elog "If you want to use rfcomm as a normal user, you need to add the user"
elog "to the uucp group."