From: "Heiko Wundram (Beenic)" <wundram@beenic.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Date: Thu, 5 Jul 2007 11:08:31 +0200
References: <200707041719.20662.wundram@beenic.net>
	<1183622671.6351.73.camel@aeonflux.holtmann.net>
In-Reply-To: <1183622671.6351.73.camel@aeonflux.holtmann.net>
MIME-Version: 1.0
Message-Id: <200707051108.32230.wundram@beenic.net>
Subject: Re: [Bluez-devel]
	=?iso-8859-1?q?Using_BlueZ_in_commercial_applicatio?=
	=?iso-8859-1?q?ns_-_Once=09again=2E?=
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="iso-8859-1"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Am Donnerstag 05 Juli 2007 um 10:04:31 schrieb Marcel Holtmann:
> there is no long reply needed. The library is GPL and this means every
> application using it has to be GPL, too. Period. No exception.

Okay. For me, this basically means that Linux cannot support commercial =

Bluetooth applications at the moment (without licensing a commercial =

Bluetooth stack), because Affix is also GPL'd, which is fine.

Anyway, this question was asked before, and never answered clearly (search =
the =

bluez-devel archives if you don't believe me), which is why I felt compelle=
d =

to ask it again, and adding this to the FAQ would IMHO make perfect sense, =
so =

that others won't have to ask it again.

> You can register SDP record via D-Bus.

Is there any documentation on this, except for the source? The Wiki doesn't =

state anything in this respect, at least not that I found.

> All BlueZ files are GPL. There is no exception and no difference between
> kernel headers and library headers. The whole kernel is covered by GPL
> and if a GPL note is missing in some files, doesn't mean that they are
> not GPL.

This is not entirely true. The kernel headers (/usr/include/linux =

and /usr/include/asm) are _mostly_ (not all, esp. not the netfilter-headers =

and some other driver headers) stripped from licensing infos by the kernels =

make process (or are auto-generated by it), and are included in libc header=
s. =

One example of such an inclusion is asm/page.h, which is used pretty widely =

in the libc headers, which are licensed under the LGPL.

If asm/page.h was GPL (the licensing info wasn't stripped or rather, =

explicitly not set by the generation process which creates the header), no =

program would be able to _not_ be GPL if it linked against the standard lib=
c =

headers (which is kind'a necessary).

This is the question that popped up in my mind when thinking about the Blue=
Z =

headers...

-- =

Heiko Wundram
Product & Application Development
-------------------------------------
Office Germany - EXPO PARK HANNOVER
=A0
Beenic Networks GmbH
Mail=E4nder Stra=DFe 2
30539 Hannover
=A0
Fon =A0 =A0 =A0 =A0+49 511 / 590 935 - 15
Fax =A0 =A0 =A0 =A0+49 511 / 590 935 - 29
Mail =A0 =A0 =A0 wundram@beenic.net


Beenic Networks GmbH
-------------------------------------
Sitz der Gesellschaft: Hannover
Gesch=E4ftsf=FChrer: Jorge Delgado
Registernummer: HRB 61869
Registergericht: Amtsgericht Hannover

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel