From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCID D-Bus
Date: Fri, 09 Sep 2005 15:40:52 +0200 [thread overview]
Message-ID: <1126273252.5227.119.camel@blade> (raw)
In-Reply-To: <20050909132940.GE17543@spring.luon.net>
Hi Sjoerd,
> > having 0.33 is better than 0.23 and this is what Debian unstable still
> > uses. However lets make a list of the distributions:
> >
> > SuSE Linux 10.0 D-Bus 0.35
> > Fedora Core 4 D-Bus 0.33
> > Ubuntu Breezy D-Bus 0.36
> > Debian unstable D-Bus 0.23
> Debian experimental D-Bus 0.50
this is good.
> > The only bad guy is Debian unstable and I don't care anymore. They use
> > Xorg finally and have GCC 4.0 etc., but they can't move over to the next
> > D-Bus generation. I think that is their problem now and the release of
> > bluez-utils-0.22 will definitely drop the support for the old D-Bus 0.23
> > version.
>
> D-bus >= 0.3x has been in debian experimental for quite some time. There are
> various transitions going on in debian unstable currently which makes it
> inappropriate to do a dbus transition now too.
Last time I looked at it, the complete KDE part was broken and full of
wrong dependencies. So breaking D-Bus wouldn't even be notified ;)
> > I like to base everything around the current D-Bus 0.50 release, because
> > the C API should be quite stable now. I will accept small workarounds to
> > make D-Bus 0.3x work, but as soon as the distributions update their
> > D-Bus libraries I will drop them.
> >
> > This is not a nice thing to do, I know, but a wrong usage of D-Bus lets
> > hcid segfault and this is not what I want.
>
> As one of debian's dbus maintainers i would advise to indeed base everything on
> dbus >= 0.50. Hopefully it won't take too long before we can move the new dbus
> from experimental to unstable, so the workarounds for old dbus release are just
> not worth it.
This means I will release bluez-utils-2.21 on the weekend, because of
some memory leak fixes and then I will drop D-Bus 0.23 support. So if
any patches need to go in before, please send them now.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-09 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 19:50 [Bluez-devel] HCID D-Bus Claudio Takahasi
2005-09-08 23:07 ` Marcel Holtmann
2005-09-09 8:25 ` Peter Robinson
2005-09-09 9:37 ` Marcel Holtmann
2005-09-09 13:29 ` Sjoerd Simons
2005-09-09 13:40 ` Marcel Holtmann [this message]
2005-09-12 21:07 ` [Bluez-devel] HCID D-Bus (Sig Fault) Claudio Takahasi
2005-09-12 21:14 ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-12 21:40 ` [Bluez-devel] HCID D-Bus (Sig Fault) Marcel Holtmann
2005-09-12 23:09 ` Claudio Takahasi
2005-09-12 23:21 ` Marcel Holtmann
2005-09-13 13:03 ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-13 18:54 ` Marcel Holtmann
2005-09-14 12:00 ` Claudio Takahasi
2005-09-14 15:16 ` Marcel Holtmann
2005-09-14 16:06 ` Claudio Takahasi
2005-09-15 8:11 ` 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=1126273252.5227.119.camel@blade \
--to=marcel@holtmann.org \
--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