[PATCH 0/5] Fix the conflict between bluetooth-policy and card-restore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4 August 2016 at 13:49, Pali Rohár <pali.rohar at gmail.com> wrote:
> On Thursday 04 August 2016 19:35:57 Tanu Kaskinen wrote:
>> This may very well cause a regression for BlueZ 4, because I didn't
>> make the corresponding changes there. The code isn't identical with
>> BlueZ 5, and it would be a bit difficult for me to test with BlueZ 4.
>> What do others think - should I nevertheless try to install BlueZ 4
>> and update the BlueZ 4 code too, or can we let the BlueZ 4 code just
>> rot?
>
> I have only Bluez 4, so please do not drop Bluez 4 code. If you to do
> testing code for Bluez 4 setup, I can do that.

Out of curiosity, what distro is this? From what I can look at, only
SourceMage still has bluez 4, and both Debian and Ubuntu moved to
bluez 5 in their latest (LTS) release.

>From what I know, the pulseaudio maintainers use Debian, Fedora and
Gentoo (I may be wrong though). As all of these distros have moved to
bluez 5, I think it is kind of inevitable that bluez 4 code will
bitrot.

-- 

Saludos,
Felipe Sateler


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux