public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred Schaettgen <bluez-devel@schaettgen.de>
To: bluez-devel@lists.sourceforge.net
Cc: "Michael 'Mickey' Lauer" <mickey@tm.informatik.uni-frankfurt.de>,
	bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Bluez without libbluez?
Date: Sat, 16 Jul 2005 00:26:47 +0200	[thread overview]
Message-ID: <200507160026.47848.bluez-devel@schaettgen.de> (raw)
In-Reply-To: <1121456287.7374.16.camel@gandalf.tm.informatik.uni-frankfurt.de>

On Friday, 15. July 2005 21:38, Michael 'Mickey' Lauer wrote:
=2E..
> As a side note, I'm wondering how libkdebluetooth and Gnome's libbtctl
> can claim that they're LGPL while linking to libbluez.

libkbluetooth is GPLed or did I miss something?
libqobex on the other hand is in fact LGPLed. But libqobex alone as source=
=20
does not derive from or use the BlueZ libs. It does once you compile it,=20
which means that the resulting programs must be GPLed. Which they are. And=
=20
besides that I won=C2=B4t care about such details unless as german court co=
mmented=20
on these linking issues. The outcome will be like throwing a dice anyway.

=46red

=2D-=20
=46red Schaettgen
bluez-devel@schaettgen.de


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-07-15 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 19:38 [Bluez-devel] Bluez without libbluez? Michael 'Mickey' Lauer
2005-07-15 22:26 ` Fred Schaettgen [this message]
2005-07-17 13:39 ` 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=200507160026.47848.bluez-devel@schaettgen.de \
    --to=bluez-devel@schaettgen.de \
    --cc=bluez-devel@lists.sf.net \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mickey@tm.informatik.uni-frankfurt.de \
    /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