Hi Sergey, Am 28.12.2015 um 12:01 schrieb Sergey Kondakov:
On 28.12.2015 13:25, Stefan Seyfried wrote:
That's a bold statement to make given that I as the "official bluez maintainer" of openSUSE (well, as official as it gets in such a doocraty :-) have never heard of any request to package such a plugin.
Besides: everyone can become maintainer of packages, so you could just step up and package it.
(It is of course entirely possible that it has an incompatible license or such, but then the "for no reason" above is again a bold statement)
Well, technically, you're right. I was too lazy to make proper OBS request or even to complain in bugzilla. There are quite a lot of instances of that. With bluez I figured that if the people making the package did see what their package's configure script has to offer and didn't enable something like this then they have some kind of strong irrational opposition to it,
No, but I certainly won't enable stuff that upstream disabled by default *and where I don't have hardware to even test*. Because if something does not work, I'm going to get the bug reports.
which sometimes happen and, weirdly, DS support never gets love it deserves anywhere. The more weird part of DS situation is that bluez creators themselves disabled it by default and didn't want to accept ready patches for it from the beginning. Instead they seem to have reimplemented them without noticeable difference, even with the same shortcomings.
To enable it you need to pass '--enable-sixaxis' configure option and add <libdir>/bluetooth/plugins/sixaxis.so file.
Ah ok. I thought it was just an addon package that just needed to be built in addition to main bluez package. Feel free to send a submitrequest against Base:System/bluez adding the enable switch. If I know that there are users and testers, I'm certainly not against enabling stuff.
Everyone can become a maintainer. But something as critical as the free Bluetooth implementation really should get attention from all the important-looking people. But then again, we're talking about the "product" where GRUB may suddenly fail to chainload (meaning, everything other than Linux fails) because of bad official patches (starting from 44:efidisk-move-device-path-helpers-in-core-for-efinet)... I should not forget to raise a stink about that where it's appropriate
Well yes, but not in this thread :-)
-_- I also should make a request for blueman-2.0.3, the only non-DE-locked bluez GUI... someday.
Well, that would be nice. I'm personally just using bluetoothctl but that's certainly not for everyone :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org