Hi Emil, On Thu, Jan 25, 2024 at 8:51 AM Emil Velikov <emil.l.velikov@xxxxxxxxx> wrote: > > On Thu, 25 Jan 2024 at 13:02, Szymon Janc <szymon.janc@xxxxxxxxxxx> wrote: > > > > Hi, > > > > On Thu, 25 Jan 2024 at 01:07, Emil Velikov via B4 Relay > > <devnull+emil.l.velikov.gmail.com@xxxxxxxxxx> wrote: > > > > > > Hello everyone, > > > > > > Here's v3 fixing a small bug with the previous patches, which was > > > tripping the CI. > > > > > > Link to the previous revision can be found below. > > > > Just a comment that external plugins support was added to avoid udev > > dependency (from sixaxis) in bluetoothd. > > (not that I have strong opinion on this, just a note, I don't remember > > exactly why it was done, maybe Marcel recalls?) > > > > Thanks, I may have some ideas why. > > About 10 years ago (or so) some distributions were shipping > libudev.so.0 while others libudev.so.1. The ABI break was minimal, > although it was a thing. > I remember us doing all sorts of hacks in Mesa trying to pick the > correct one, esp when your system can have .1 while the game (or its > chroot-like environment) has .0 and vice-versa. > > I would imagine a similar issue was observed in bluez - but I can only > speculate. > > Over the last 5+ years, literally all supported distributions have > moved for libudev.so.1 and the Steam games (and runtime) has both with > some compat quirks to avoid explosions. I was considering applying this week but if you want to respin this set to sort out the dependency Im fine with, but I don't think it would hurt to have a libudev dependency provide we have some means to disable it in case the system don't intend to support sixaxis plugin. -- Luiz Augusto von Dentz
