linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: Vinicius Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd-0.21: configure doesn't work as expected
Date: Fri, 19 Feb 2010 18:40:25 +0100	[thread overview]
Message-ID: <1266601225.5249.25.camel@localhost.localdomain> (raw)
In-Reply-To: <2a9506371002190924p2ff4ff6eq243dc3031ae3b3a7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

El vie, 19-02-2010 a las 14:24 -0300, Vinicius Gomes escribió:
> 
> 2010/2/19 Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>:
> > Ah, then, why is plugins folder being created even if nothing will be
> > installed in it?
> >
> 
> Nothing is installed right now. But it doesn't mean that nothing will
> ever be ;-)
>
> And if you want to have a custom plugin for some application, you just write
> it and install it there, no need to mess with core obexd.
> 

True, silly me! 

> >> Thanks for the report, this is a bug. There's a patch for it in my
> >> development tree. Waiting for review.
> >>
> >> But before the next release happens, disabling a plugin is equivalent
> >> to setting its value to dummy, i.e.
> >> --without-phonebook (if it worked ;-) would be the same as
> >> --with-phonebook=dummy.
> >>
> >
> > Great, where could I see your development tree?
> >
> 
> Sure. Forgot the link, here it is:
> http://git.infradead.org/users/vcgomes/obexd.git (devel branch)
> 
Great :-D

Thanks and best regards

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-02-19 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 11:13 obexd-0.21: configure doesn't work as expected Pacho Ramos
2010-02-19 15:01 ` Vinicius Gomes
2010-02-19 15:07   ` Pacho Ramos
2010-02-19 17:24     ` Vinicius Gomes
2010-02-19 17:40       ` Pacho Ramos [this message]

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=1266601225.5249.25.camel@localhost.localdomain \
    --to=pacho@condmat1.ciencias.uniovi.es \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@openbossa.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;
as well as URLs for NNTP newsgroup(s).