From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: "Patrick Laplante" To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C6502F.6AE7D0E0" Message-ID: Subject: [Bluez-users] Question about licensing! Sender: bluez-users-admin@lists.sourceforge.net Errors-To: bluez-users-admin@lists.sourceforge.net Reply-To: bluez-users@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ users List-Post: List-Help: List-Subscribe: , List-Archive: Date: Sat, 25 Mar 2006 17:13:14 -0500 This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C6502F.6AE7D0E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi all, I am currently working on a Linux based project that need Bluetooth support. I need to basically receive images from Bluetooth devices and print them. The code printing the images is proprietary and can't be GPL'd. Since bluez is GPL, I can't just link against it without being forced to make my code GPL which I can't, my customer won't allow me to release their IP to the public. I was thinking of doing this: A small daemon that uses the bluez library that would, on image reception from a device, push the image to another print daemon over a name pipe or socket. Does this break the GPL in any way? If I understand the license correctly, I would have to make my Bluetooth daemon GPL but my print daemon wouldn't have to be GPL. Can you please confirm? Do you guys have any issue with that? The last thing I want to do is upset anybody or put my customer in a position where he could be sued. Worst case, I'll have to buy a stack from a company like StoneStreet or implement a custom stack for my customer (which will bump the price by a lot :-)). Regards, Pat Laplante Principal Engineer Vanteon Corporation 2851 Clover Street Pittsford, NY 14534-1711 Office: (585) 248-0510 x298 Fax: (585) 248-0537 www.vanteon.com - Embedded for Your Future ------=_NextPart_000_0016_01C6502F.6AE7D0E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

I am currently working on a Linux based project that = need Bluetooth support.  I need to basically receive images from Bluetooth devices = and print them.

 

The code printing the images is proprietary and = can’t be GPL’d.

 

Since bluez is GPL, I can’t just link against = it without being forced to make my code GPL which I can’t, my = customer won’t allow me to release their IP to the public.

 

I was thinking of doing = this:

 

A small daemon that uses the bluez library that = would, on image reception from a device, push the image to another print daemon = over a name pipe or socket.  Does this break the GPL in any way?  If = I understand the license correctly, I would have to make my Bluetooth daemon GPL but my = print daemon wouldn’t have to be GPL.

 

Can you please confirm?  Do you guys have any = issue with that?

 

The last thing I want to do is upset anybody or put = my customer in a position where he could be sued.  Worst case, = I’ll have to buy a stack from a company like StoneStreet or implement a custom stack = for my customer (which will bump the price by a lot J).<= /p>

 

Regards,

 

Pat = Laplante
Principal Engineer

Vanteon Corporation
2851 Clover = Street
Pittsford, = NY 14534-1711
Office: (585) 248-0510 x298
Fax: (585) 248-0537
www.vanteon.com - Embedded for Your Future =

 

------=_NextPart_000_0016_01C6502F.6AE7D0E0-- ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users