From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29338 invoked by alias); 30 Oct 2003 11:17:16 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 29313 invoked from network); 30 Oct 2003 11:17:14 -0000 Received: from unknown (HELO www.sveasoft.com) (213.242.178.190) by sources.redhat.com with SMTP; 30 Oct 2003 11:17:14 -0000 Received: from sveasoft.com (du-31-211.ppp.telenordia.se [62.127.31.211]) by www.sveasoft.com (8.12.8/8.12.5) with ESMTP id h9UADHaM016258 for ; Thu, 30 Oct 2003 11:13:17 +0100 Message-ID: <3FA0F2D3.2080802@sveasoft.com> Date: Thu, 30 Oct 2003 11:17:00 -0000 From: James Ewing Organization: Sveasoft Ltd. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030620 X-Accept-Language: en-us, sv, en MIME-Version: 1.0 To: pthreads-win32@sources.redhat.com Subject: Re: changing pthreads-win32 license - Practical Comment References: <01a101c39ed3$79f519e0$2b01a8c0@moose> In-Reply-To: <01a101c39ed3$79f519e0$2b01a8c0@moose> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003/txt/msg00125.txt.bz2 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