From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15310 invoked by alias); 23 May 2003 05:13:57 -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 15218 invoked from network); 23 May 2003 05:13:54 -0000 Received: from unknown (HELO murray.nsw.cmis.CSIRO.AU) (130.155.16.3) by sources.redhat.com with SMTP; 23 May 2003 05:13:54 -0000 Received: from darkside-nh.nsw.cmis.csiro.au (darkside-nh.nsw.cmis.CSIRO.AU [130.155.23.99]) by murray.nsw.cmis.CSIRO.AU (Postfix) with ESMTP id D745979; Fri, 23 May 2003 15:13:52 +1000 (EST) Received: from darkside-nh.nsw.cmis.csiro.au (localhost.localdomain [127.0.0.1]) by darkside-nh.nsw.cmis.csiro.au (8.12.8/8.12.8) with ESMTP id h4N5DqUW024623; Fri, 23 May 2003 15:13:52 +1000 Received: from darkside-nh.nsw.cmis.csiro.au (talbot@localhost) by darkside-nh.nsw.cmis.csiro.au (8.12.8/8.12.8/Submit) with ESMTP id h4N5DfZN024619; Fri, 23 May 2003 15:13:41 +1000 Message-Id: <200305230513.h4N5DfZN024619@darkside-nh.nsw.cmis.csiro.au> To: pthreads-win32@sources.redhat.com Cc: VGandhi@quark.co.in, vkt@india.hp.com, Jay.Turner@sabre-holdings.com Subject: Re: LGPL and a proprietary application In-reply-to: Your message of Fri, 23 May 2003 09:41:56 +0530. <7D5800A5B6E26644B2EB7A862856B0D407EF7ABC@SARASWATI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 May 2003 05:13:00 -0000 From: Hugues Talbot X-SW-Source: 2003/txt/msg00054.txt.bz2 Hi Vikas, Caveat: I am not a lawyer, you should contact one if you have any doubt. Vinaya is basically right in telling you to link with a shared library (DLL) version of pthread-win32, this puts you in the clear as far as the LGPL is concerned (section 6 allows specifically for that case). The wording of section 5. of the license is not as clear cut if you want to use a static version (.LIB version), therefore it is not simple to answer your questions: > 1) Is usage of a product like "pthreads-win32" forces us to release our > source code or not. Generally, if you are not modifying the pthreads-win32 library or taking a significant portion of it in your own code (as in cutting-and-pasting some portion of the pthread-win32 source code), then you do not need to release your source code. If you are modifying the pthreads-win32 library (say if you need to modify some internal parameters, or if you fix a bug that you have found), you fall under the scope of the LGPL and you must release at least your changes to the library, and possibly more (say if you added some significant enhancements to the library to handle cases that it doesn't handle now, you would be required to publish those, enough that others would be able to use them). 2) Next can we use it as per our with without intimating anyone. I'm not sure what you mean by that. You certainly cannot use pthreads-win32 as if it were your own code. Is that what you mean? -------- Hugues Talbot, CSIRO Mathematical & Information Sciences Locked Bag 17, Building E6B, Macquarie University North Ryde NSW 2113 Australia Ph: 61 2 9325 3208 Fax: 61 2 9325 3200 63% of all statistics are made up on the spot.