All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: pkg-bluetooth-maintainers@lists.alioth.debian.org,
	Bram Stolk <bram@sara.nl>
Subject: Re: [Bluez-devel] [Pkg-bluetooth-maintainers] dbus dependency	introduces unwanted X11 dependency
Date: Mon, 25 Dec 2006 18:14:16 +0100	[thread overview]
Message-ID: <1167066856.11510.22.camel@violet> (raw)
In-Reply-To: <20061225165542.GA970@esaurito.net>

Hi Filippo,

> > I'm currently running bluez-utils version 2.25-1
> > 
> > Upgrading to 3.7-1 gives me the following problem:
> > 
> > I have a server running Debian/testing.
> > I want to keep this server completely free from XWindow stuff.
> 
> on a clean etch system the installation of bluez-utils brings in the following
> packages:
> 
> dbus libbluetooth2 libdbus-1-3 libexpat1 libx11-6 libx11-data libxau6 libxdmcp6
> x11-common
> 
> the only x-related stuff is the x11 client libraries and x11-common, totalling
> 4MB of diskspace, you won't be able to run an X server with any of those
> packages.
> 
> > 
> > However, this server is to act as a bluetooth accesspoint using
> > the PAN profile, and the pand deamon.
> > 
> > This works fine with version 2.25-1 of bluez-utils/
> > 
> > With the new version, dbus gets pulled in. Why?
> > Isn't libdbus enough?
> 
> starting with bluez 3.x most of the functionality has been moved to dbus, which
> is used among other things for pinhelper functionalities.
> and no, libdbus isn't enough unless I'm missing something, bluez (hcid) needs to
> register to the local dbus.

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.

> > This is so ugly...
> > 
> > It should be possible to run pand without the X11 burden.
> > It used to be possible in the past, but not anymore.
> 
> I'm not sure if it makes any sense to have bluetooth daemons splitted in its own
> package. 

No. All of them will be extended with D-Bus functionality anyway. D-Bus
is the way to go and people fighting it are on a dead end.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-12-25 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1167052771.5265.7.camel@suske>
2006-12-25 16:55 ` [Bluez-devel] [Pkg-bluetooth-maintainers] dbus dependency introduces unwanted X11 dependency Filippo Giunchedi
2006-12-25 17:14   ` Marcel Holtmann [this message]
2006-12-25 17:53     ` Bram Stolk
2006-12-25 18:11       ` Marcel Holtmann
2006-12-25 18:30         ` Bram Stolk
2006-12-25 18:43           ` Marcel Holtmann
2006-12-25 18:12     ` Filippo Giunchedi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1167066856.11510.22.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bram@sara.nl \
    --cc=pkg-bluetooth-maintainers@lists.alioth.debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.