From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ licensing inquiry
Date: Tue, 29 Mar 2005 07:44:39 +0200 [thread overview]
Message-ID: <1112075079.9016.58.camel@pegasus> (raw)
In-Reply-To: <OF200FCC20.5703443A-ON48256FD3.001D7002-48256FD3.001DBAF3@lexmark.com>
Hi Gail,
> I would like to know, what is the licensing for BlueZ? Are there any
> issues from a legal or licensing stand-point if we port it to another
> OS?
the license of the BlueZ source code is GPL. However I am not sure if it
makes sense at all to port it to another operating system. The kernel
part is deeply based on Linux specific structures.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-03-29 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 5:23 [Bluez-users] BlueZ licensing inquiry gcagasan
2005-03-29 5:36 ` Michal Semler
2005-03-29 5:44 ` Marcel Holtmann [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=1112075079.9016.58.camel@pegasus \
--to=marcel@holtmann.org \
--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