If someone is emerging the obexd package, they are generally expecting to install the obexd binary. The default USE flags should include server, or the package should be renamed to obex. I'm filing this as an Enhancement Request, although I consider it to be a logical and semantic bug in the ebuild design Reproducible: Always
This is intentional since obexd server is not used by any app, while apps in the tree requiring a server are using obex-data-server one (that conflicts with obexd one). This is why I prefer to, even letting people to install obexd server with USE, default to: - client provided by obexd - server provided by obex-data-server This situation is the root cause of other distributions (like, for example, fedora) don't even providing obexd server at all (or, at least, when I checked it in the past). For a better explanation, please review: http://bugs.gentoo.org/show_bug.cgi?id=302727 (specially from comment #19) https://bugzilla.gnome.org/show_bug.cgi?id=609858 In summary, I won't enable server USE flag by default since obexd server is not widely used and it would create blockers with obex-data-server in a lot of common setups that simply want to get, for example, gnome-bluetooth "working" Best regards
I would argue that if this is the case, the package should be named obex, then. Calling a package obexd and then not actually supplying obexd is semantically wrong
