public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Filippo Giunchedi <filippo@esaurito.net>
To: Bram Stolk <bram@sara.nl>
Cc: pkg-bluetooth-maintainers@lists.alioth.debian.org,
	bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [Pkg-bluetooth-maintainers] dbus dependency introduces unwanted X11 dependency
Date: Mon, 25 Dec 2006 17:55:42 +0100	[thread overview]
Message-ID: <20061225165542.GA970@esaurito.net> (raw)
In-Reply-To: <1167052771.5265.7.camel@suske>

Hi, [upstream CCed]

On Mon, Dec 25, 2006 at 02:19:31PM +0100, Bram Stolk wrote:
> Hi there,
> 
> 
> 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.

> 
> And with dbus, X11 is introduced.

not exactly, a small part of an X11 client is introduced.

> 
> 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. 

thanks for your report,
filippo

-------------------------------------------------------------------------
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 16:55 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 ` Filippo Giunchedi [this message]
2006-12-25 17:14   ` [Bluez-devel] [Pkg-bluetooth-maintainers] dbus dependency introduces unwanted X11 dependency Marcel Holtmann
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=20061225165542.GA970@esaurito.net \
    --to=filippo@esaurito.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox