So I want to try and play around with a particular network domination tool
on my home network, Omphalos. However, its current configure script has a
hard dependency on bluetooth.h, part of the net-wireless/bluez package.
Currently, net-wireless/bluez has a harddep on virtual/udev, which works
great if you use either udev or eudev. I'm using busybox's mdev instead, so
the logic of the bluez ebuild needs some changes:
--- bluez-5.15.ebuild 2014-03-08 21:13:24.049329018 -0500
+++ bluez-5.15-r1.ebuild 2014-03-08 21:17:28.029686862 -0500
@@ -16,3 +16,3 @@ SLOT="0/3"
KEYWORDS="~amd64 ~arm ~hppa ~ppc ~ppc64 ~x86"
-IUSE="cups debug +obex readline selinux systemd test"
+IUSE="cups debug +obex readline selinux systemd test udev"
REQUIRED_USE="test? ( ${PYTHON_REQUIRED_USE} )"
@@ -23,3 +23,4 @@ RDEPEND="
>=sys-apps/hwids-20121202.2
- >=virtual/udev-171
+ udev? ( >=virtual/udev-171 )
+ !udev? ( virtual/dev-manager )
cups? ( net-print/cups:= )
@@ -94,3 +95,3 @@ src_configure() {
--enable-monitor \
- --enable-udev \
+ $(use_enable udev) \
$(use_enable cups) \
@@ -136,3 +137,5 @@ pkg_postinst() {
- udev_reload
+ if use udev ; then
+ udev_reload
+ fi
Thoughts on this?
The other option is to split the libbluetooth bits out from bluez and put
them into their own package. This would be equivalent to Debian's
libbluetooth-dev it looks. Anyone know of any other use cases where a
separate libbluetooth package would be useful?
Omphalos:
http://nick-black.com/dankwiki/index.php/Omphalos
--
Joshua Kinard
Gentoo/MIPS
[email protected]
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
