All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: acr@acroberts.com,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Windows Port
Date: Wed, 28 Jan 2004 08:53:08 +0100	[thread overview]
Message-ID: <1075276388.12766.49.camel@pegasus> (raw)
In-Reply-To: <50BF37ECE4954A4BA18C08D0C2CF88CB04B83F@exmail1.se.axis.com>

Hi Peter,

> I may be stating the obvious, but do not forget about the 
> license issue. As far as I can tell from a quick search 
> through the BlueZ repository, only the code in libs2/lib 
> and utils2/lib is under LGPL, the rest (including the "old" 
> libraries) are under GPL. This means that any program or
> kernel driver that uses any of the GPLed parts need to be 
> GPLed too. (This, btw, goes for Linux applications too that 
> use or link with the GPLed parts.)

actually there is no problem with GPL or LGPL software on the Windows
platform, but you are right that every kernel driver or program must be
licensed under GPL, too.

The libs2 is not really LGPL at the moment (even if the header of the
files say so). Max and I already agreed that we should make the new
library LGPL, but there are still some code snippets that are copyright
by Qualcomm. And this code is GPL only at the moment, which means that
the complete code will be still under the GPL. Maybe it is a good time
to discuss this now. Max, what is the current status on this?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-28  7:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  7:33 [Bluez-devel] Windows Port Peter Kjellerstedt
2004-01-28  7:53 ` Marcel Holtmann [this message]
2004-01-28  7:58   ` Antony C. Roberts
2004-01-28  8:08     ` Marcel Holtmann
2004-01-28  8:18       ` Antony C. Roberts
2004-01-28 16:22         ` Marcel Holtmann
2004-01-28 19:55           ` Antony C. Roberts
  -- strict thread matches above, loose matches on Subject: below --
2004-01-27  8:54 Antony C. Roberts
2004-01-27 13:59 ` Marcel Holtmann
     [not found]   ` <46161.80.63.28.114.1075214415.squirrel@acroberts.com>
2004-01-27 14:25     ` Marcel Holtmann
     [not found]       ` <46892.80.63.28.114.1075215434.squirrel@acroberts.com>
     [not found]         ` <48760.80.63.28.114.1075219113.squirrel@acroberts.com>
2004-01-27 16:38           ` Marcel Holtmann

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=1075276388.12766.49.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=acr@acroberts.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=peter.kjellerstedt@axis.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.