From: "Patrick Laplante" <plaplante@vanteon.com>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Question about licensing!
Date: Sat, 25 Mar 2006 17:13:14 -0500 [thread overview]
Message-ID: <E1FNH0j-0003Bs-QK@mail.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
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 <http://www.vanteon.com> - Embedded for Your Future
[-- Attachment #2: Type: text/html, Size: 6336 bytes --]
next reply other threads:[~2006-03-25 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 22:13 Patrick Laplante [this message]
2006-03-25 23:29 ` [Bluez-users] Question about licensing! Alec Myers
2006-03-25 23:55 ` Patrick Laplante
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=E1FNH0j-0003Bs-QK@mail.sourceforge.net \
--to=plaplante@vanteon.com \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).