public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [BlueZ-Announce] Release of	bluez-libs-3.26	and	bluez-utils-3.26
Date: Mon, 11 Feb 2008 01:47:34 +0000	[thread overview]
Message-ID: <1202694454.3491.129.camel@cookie.hadess.net> (raw)
In-Reply-To: <1202693468.7664.135.camel@violet>


On Mon, 2008-02-11 at 02:31 +0100, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > > this is an update release of the new stable versions of the Bluetooth
> > > library and the utilities. This release is actually a cleanup release
> > > and the first step towards the BlueZ 4.0 generation.
> > > 
> > > With this release all services are switched on by default and all old
> > > school daemons are disabled. So all package maintainers, please keep
> > > this in mind and adjust your packages.
> > > 
> > > The sources can be found at http://www.bluez.org/download.html
> > 
> > Which daemons do you call "old school"? Is this pand/dund?
> 
> yes. All this hidd, pand, dund etc. stuff that is more hacking around
> than actually doing something.

Right, we weren't using those by default in Fedora either.

> > Can we get rid of the tick boxes in the properties services tab now? :)
> 
> Actually we will, but not so quickly. We have to re-design parts of the
> service infrastructure for 4.0 and then we see.

OK.

> Btw. you need to update gnome-user-share since the obex-data-server-0.1
> API now uses DBUS_TYPE_OBJECT_PATH and no strings anymore.

I didn't see anything to port at first glance, but you're right. Fixed
in SVN trunk.

> And I am thinking about simply adding the support for FTP to bluez-gnome
> since the dependencies of gnome-user-share are a little bit too much.

The same as bluez-gnome plus httpd and avahi. Could you add a way to
disable the bluez-gnome code? I'm thinking of adding obexpush support in
gnome-user-share as well, as it's the better place to have it, thinking
desktop-wide.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-02-11  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1202692346.7664.129.camel@violet>
2008-02-11  1:23 ` [Bluez-devel] [BlueZ-Announce] Release of bluez-libs-3.26 and bluez-utils-3.26 Bastien Nocera
2008-02-11  1:31   ` Marcel Holtmann
2008-02-11  1:47     ` Bastien Nocera [this message]
2008-02-11  2:33       ` 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=1202694454.3491.129.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --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