Linux bluetooth development
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Dealing with the bluez-utils dependencies
Date: Tue, 10 May 2005 10:04:30 -0300	[thread overview]
Message-ID: <e1effdeb05051006043be12b4a@mail.gmail.com> (raw)
In-Reply-To: <1115722824.8949.242.camel@pegasus>

Hi Marcel,

Regarding D-Bus support for pand and hcid.=20
DBUS is under development and there is backward compatibility problem.
Some APIs changed, I suggest check the dbus version at build time=20
and fix the code to support this. The latest version(0.33) is not compatibl=
e
with 0.23.


Regards,
Claudio




On 5/10/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Folks,
>=20
> the dependency list of bluez-utils is going to be crazy and I think we
> need to work on some parts. I can't be possible that if you install
> bluez-utils that GTK+ and Python will be installed in some cases.
>=20
> The base dependency is the C library and bluez-libs or libbluetooth and
> this will not change of course ;)
>=20
> So lets talk about the other packages we need and use. The first one is
> the USB library that we need. It is used by hid2hci, bcm203x and dfutool
> programs. While bcm203x is only needed for the 2.4 kernel series and
> should be always kept as a separate package, I don't consider this a
> problem. Most modern distributions won't need this tool. The dfutool is
> only needed by developers and people that play with firmware upgrades.
> However it might be handy to create a bluez-devel packages that depends
> on the Bluetooth library header files and gives you special tools for
> the developers. Such a package may also contain the *test applications.
> However I think that people who wants to play with firmware upgrades
> should maybe better compile dfutool by themself. So at least it is not
> that easy to screw a Bluetooth device and then try to blame others. My
> only problematic tool left with USB dependency is hid2hci and this is
> really needed for all of you using HID Proxy dongles. So do you think a
> general dependency on the USB library is fine for a bluez-utils binary
> package?
>=20
> Next big thing is the D-Bus library. We use D-Bus in hcid and it seems
> that people are working on D-Bus support for pand. Personal I am not a
> big believer in D-Bus anymore, but it gets used and so we can't avoid
> it. So should we leave that a compile time option and by default we
> enable it. The bluez-utils binary package then simply depends on the
> D-Bus library?
>=20
> With configure we also check for OpenOBEX and ALSA. The OpenOBEX part is
> not ready at the moment and still part of its own in the CVS. For ALSA
> we now have the first draft of an A2DP plugin. However I think most
> packages maintainers will create a bluez-alsa package for it and this
> looks like a sane thing to me.
>=20
> And now the really ugly part. The PIN helper support. This is the real
> pain and we should find a nice solution for it. The original Python
> script is not an option, because it depends on Python and even the GTK
> PIN helper will add the GTK+ libraries. Also the KDE Bluetooth project
> has its own PIN helper. I personal like to go with the SuSE idea to
> provide a general PIN helper script that checks the installed tools and
> then executes the right PIN helper or provides a default PIN (or no PIN)
> if nothing has been setup. We can also add more config options, where we
> provide a list of PIN helpers that will tried one after the other. Maybe
> also a default PIN option would be a good idea. Comments please.
>=20
> Regards
>=20
> Marcel
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=3D7393&alloc_id=3D16281&op=3Dclick
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>=20


--=20
_______________________________________
Claudio Takahasi
INdT - Nokia Technology Institute
Phone: +55 81 21223034
Recife - Pernambuco - Brazil


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-05-10 13:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 11:00 [Bluez-devel] Dealing with the bluez-utils dependencies Marcel Holtmann
2005-05-10 13:04 ` Claudio Takahasi [this message]
2005-05-12 12:40   ` Marcel Holtmann
2005-05-12 12:53     ` Claudio Takahasi
2005-05-12 13:03       ` Marcel Holtmann
2005-05-16 17:04         ` Claudio Takahasi
2005-05-16 17:34           ` Marcel Holtmann
2005-05-10 15:25 ` Brad Midgley
2005-05-10 15:46   ` Marcel Holtmann
2005-05-10 21:40     ` Claudio Takahasi
2005-05-11 16:59       ` Marcel Holtmann
2005-05-11  0:13     ` Brad Midgley
2005-05-11 11:19       ` Marcel Holtmann

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=e1effdeb05051006043be12b4a@mail.gmail.com \
    --to=cktakahasi@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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