From: "Phil Frisbie, Jr." <phil@hawksoft.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: changing pthreads-win32 license
Date: Fri, 31 Oct 2003 16:27:00 -0000 [thread overview]
Message-ID: <3FA28D50.30503@hawksoft.com> (raw)
In-Reply-To: <3FA20890.5050005@callisto.canberra.edu.au>
Ross Johnson wrote:
> Alexander Terekhov wrote:
>
>>> It specifically exempts macro definitions and the like. Read it.
>>
>> You mean "ten lines or less in length"? Yeah, given that the length of
>> lines seem to be unrestricted. [L]GPL is totally brian-damaged
>> technically and legally. Really.
>>
> Personally, I'd be inclined to regard any work that included only
> the unmodified LGPL'ed header files, specifically supplied for that
> purpose, and dynamically linked to the unmodified main body of the
> library, to be an independent and separate work as far as the LGPL
> goes - static linking and assorted tricks aside for the moment.
Sony Entertainment's lawyers did not seem to have a problem including my LGPL'ed
HawkVoice library as a DLL in their new game Planetside.
--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
prev parent reply other threads:[~2003-10-31 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F9347E8.1080105@callisto.canberra.edu.au>
2003-10-20 10:06 ` Alexander Terekhov
2003-10-30 7:03 ` Ross Johnson
2003-10-30 9:51 ` Alexander Terekhov
2003-10-30 10:49 ` Will Bryant
2003-10-30 11:17 ` changing pthreads-win32 license - Practical Comment James Ewing
2003-10-30 11:46 ` changing pthreads-win32 license Alexander Terekhov
2003-10-30 13:14 ` UNSUBCRIBE Geoffrey Atkinson
2003-10-31 7:00 ` changing pthreads-win32 license Ross Johnson
2003-10-31 10:56 ` Alexander Terekhov
2003-10-31 16:27 ` Phil Frisbie, Jr. [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=3FA28D50.30503@hawksoft.com \
--to=phil@hawksoft.com \
--cc=pthreads-win32@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).