[Bluez-devel] [Pkg-bluetooth-maintainers] dbus dependency introduces unwanted X11 dependency

[Marcel Holtmann]

Hi Bram,

> > > > the bluez-utils depends on a working D-Bus system bus. It has no
> > > > dependency on X or anything else (besides the Bluetooth library). So if
> > > > it pulls in X related stuff then this is a fault of D-Bus or its package
> > > > and not a problem within the bluez-utils package.
> > > 
> > > I'll take this up with the dbus maintainer then.
> > > 
> > > I still think that there is no need for X11 client stuff if you
> > > want to run a PAN daemon. Bluetooth communication has nothing to
> > > do with graphics devices. The 2.x version of bluez-utils demonstrated
> > > it can do without.
> > 
> > you still don't understand it. BlueZ is _not_ using any X functionality
> 
> With all due respect:
> 
> I think it is you who does not understand (or not read).
> In my very first mail I wrote:
> "And with dbus, X11 is introduced."

you wrote "Bluetooth communication has nothing to do with graphics ..."
and that is even more true with the bluez-utils-3.x packages since we
dropped the PIN helper which could have introduced a Python-GTK
dependency and was really pulling in unneeded packages. All
communication is done via D-Bus and this makes it language independent
and also graphical desktop independent.

You comparison between how 2.x is working and how 3.x is doing things
simply doesn't work here. Major version are meant to break things or do
things completely different.

> > in its daemons. We never have and we never will be. Period. However we
> > use D-Bus as general communication method and that is a hard dependency
> > now and it won't change in the future. So if you wanna use something
> > that doesn't use D-Bus then stick to the 2.x releases. There was a
> > reason why we changed the major version number.
> 
> Ok, fine.
> It's just that when you compare dependencies between 2.x and 3.x, it 
> is *not* that the communication method changed: libdbus was a dependency
> for both versions. I do not think that you realized this.

This is not important, because you have hard (mandatory) and soft
(optional) dependency and you simply can't express these within a binary
package. You must look at the source package to see how that works.

Regards

Marcel