From: James Ewing <james.ewing@sveasoft.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: changing pthreads-win32 license - Practical Comment
Date: Thu, 30 Oct 2003 11:17:00 -0000 [thread overview]
Message-ID: <3FA0F2D3.2080802@sveasoft.com> (raw)
In-Reply-To: <01a101c39ed3$79f519e0$2b01a8c0@moose>
While working as a consultant a couple of years ago, I suggested using
the phreads-win32 library as part of a cross-platform (*nix/Windows)
product. We moved ahead with pthreads-win32 on Windows and POSIX
pthreads on *nix. Unfortunately when legal reviewed the licenses, the
"new, improved" LGPL version had been released. Legal refused to approve
the product with the LGPL code and the WIN32 version was dropped (as
was my contract about 2 months later - I took major heat for the call to
use an LGPL lib).
If the intent is to offer pthreads-win32 for commercial use, the LGPL is
not an acceptable risk in certain commercial enterprises.
Just thought I'd add a practical comment to the licensing discussion.
Best Regards,
James Ewing
next prev parent reply other threads:[~2003-10-30 11:17 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 ` changing pthreads-win32 license 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 ` James Ewing [this message]
2003-10-30 11:46 ` 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.
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=3FA0F2D3.2080802@sveasoft.com \
--to=james.ewing@sveasoft.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).