Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 392879 - net-wireless/bluez-4.96-r1 should have wiimote support (by xwiimote)
Summary: net-wireless/bluez-4.96-r1 should have wiimote support (by xwiimote)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Tiziano Müller (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-02 01:51 UTC by Otamay
Modified: 2011-12-31 21:09 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
The patch just adds wiimote USE FLAG to compile bluez with wiimote support. (bluez-add-wiimote-support.patch,728 bytes, patch)
2011-12-02 01:53 UTC, Otamay
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Otamay 2011-12-02 01:51:41 UTC
net-wireless/bluez-4.96-r1 should have wiimote support.

With a "wiimote" use flag enabled and a kernel with xwiimote support (hid-wiimote module), the system can connect very easly a wiimote through bluetooth system only.

Reproducible: Always

Steps to Reproduce:
1.`emerge -v net-wireless/bluez`.
2.load hid-wiimote module.
3.try to pair the wiimote through bluetooth device manager (like bluedevil).
Actual Results:  
Bluez can't pair with the wiimote via hid-wiimote module.

Other methods for using wiimote (like cwiid) works well.

Expected Results:  
Bluez should connect to the wiimote.

By adding a USE flag in the original ebuild, bluez can be successfully compiled with wiimote support.

The changes made on bluez-4.96-r1 would be:

--- /usr/portage/net-wireless/bluez/bluez-4.96-r1.ebuild        2011-08-01 04:49:02.000000000 -0500
+++ /usr/local/portage/net-wireless/bluez/bluez-4.96-r2.ebuild  2011-12-01 16:53:28.362997026 -0600
@@ -19,7 +19,7 @@
 SLOT="0"
 KEYWORDS="~amd64 ~arm ~hppa ~ppc ~ppc64 ~x86"
 
-IUSE="alsa caps +consolekit cups debug gstreamer maemo6 health old-daemons pcmcia pnat test-programs usb"
+IUSE="alsa caps +consolekit cups debug gstreamer maemo6 health old-daemons pcmcia pnat test-programs usb wiimote"
 
 CDEPEND="
        >=dev-libs/glib-2.14:2
@@ -100,7 +100,8 @@
                $(use_enable pcmcia) \
                $(use_enable pnat) \
                $(use_enable test-programs test) \
-               $(use_enable usb)
+               $(use_enable usb) \
+               $(use_enable wiimote)
 }
 
 src_install() {
Comment 1 Otamay 2011-12-02 01:53:13 UTC
Created attachment 294469 [details, diff]
The patch just adds wiimote USE FLAG to compile bluez with wiimote support.
Comment 2 Pacho Ramos gentoo-dev 2011-12-31 21:09:41 UTC
*bluez-4.97-r1 (31 Dec 2011)
*bluez-4.97 (31 Dec 2011)

  31 Dec 2011; Pacho Ramos <pacho@gentoo.org> +files/bluez-4.67-udev.script,
  -bluez-4.96-r2.ebuild, +bluez-4.97.ebuild, +bluez-4.97-r1.ebuild,
  +files/rfcomm-conf.d, +files/rfcomm-init.d:
  Version bump that also includes IMPORTANT changes:
  - old-daemons were dropped because they are poorly maintained and I am unable
    to test them. Also have some problems and look to not work at all in default
    setups (bug #381355 by Agostino Sarubbo and Rafał Mużyło). If you think you
    still need some of them, please open a new bug report explaining your needs
    to let us find a replacement or, if none is available, readd only needed old
    daemons.
  - 'bluetooth' init.d script has been completely removed as it was only
    calling "udevadm trigger --subsystem-match=bluetooth --action=add" at startup.
    This instruction is now called directly by /lib/udev/bluetooth.sh (the one that
    was previously calling init.d script and causing problems on systemd setups as
    reported by mgorny and others (bug #396403), this should also solve bug #389531.
    Due this change, it's possible that you will start to see how your bluetooth
    device is not properly detected just after booting if not manually running
    "udevadm trigger --subsystem-match=bluetooth --action=add", if this is your case,
    please report a bug to readd a bluetooth init.d script for that (even without
    getting it automatically started by udev to not hurt systemd users).
  - Because of previous change, 'rfcomm' part of old bluetooth init.d script has been
    moved to its own script under /etc/init.d and conf.d.
  - Due bug 392879 (by Otamay) I have rethink the way some plugins were being 
    installed or not to simply always build and install them. This adds no additional
    dependencies, also simplifies ebuild preventing it from growing forever with a
    lot of USE flags and, probably the most important one, makes bluez to simply
    support and work with more devices.
  Also remove old.