Linux bluetooth development
 help / color / mirror / Atom feed
From: "Gary Alistair Macritchie" <x04-gma@dsv.su.se>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] BlueZ in non-GPL software
Date: Mon, 18 Jun 2007 19:33:47 +0200 (CEST)	[thread overview]
Message-ID: <60617.213.100.27.27.1182188027.squirrel@mail.dsv.su.se> (raw)
In-Reply-To: <20070618162819.GK30167@sorvankyla.yok.utu.fi>

Hiya,

I've had a good check through this mailing list about the question of
whether the Bluez files can be used when creating proprietary software,
but the last thread on this fizzled out before a solid answer.

What is the current view on whether the kernel modules, packages,
libraries etc. can be used in non-GPL software?

A specific example would be using the "bluez-hcidump" package with a
non-GPL piece of software.

Looking forward to a reply!
X04


-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-06-18 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 16:28 [Bluez-users] Are Gembird and Targus usb bluetooth dongles going to be supported? Mikko Tuumanen
2007-06-18 17:33 ` Gary Alistair Macritchie [this message]
2007-06-18 19:25   ` [Bluez-users] BlueZ in non-GPL software Matti Katila
2007-06-18 17:59 ` [Bluez-users] Are Gembird and Targus usb bluetooth dongles going to be supported? Mikko Tuumanen

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=60617.213.100.27.27.1182188027.squirrel@mail.dsv.su.se \
    --to=x04-gma@dsv.su.se \
    --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