From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100376 invoked by alias); 26 Feb 2020 21:04:20 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 100331 invoked by uid 89); 26 Feb 2020 21:04:16 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_50,KAM_SHORT,RCVD_IN_DNSWL_LOW,TBC autolearn=no version=3.3.1 spammy=officers, donated, compliance, mrpmghost X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.138) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 26 Feb 2020 21:04:14 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id 73qljFsjbRnrK73qmj9yiQ; Wed, 26 Feb 2020 14:04:13 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: cygwin licensing question To: cygwin@cygwin.com References: From: Brian Inglis Message-ID: <3472932c-fd8f-fea6-21e8-01d8a06cd546@SystematicSw.ab.ca> Date: Wed, 26 Feb 2020 21:04:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00244.txt.bz2 On 2020-02-26 09:37, MrPmghost . wrote: > I am Pierre Meignen, software developer working for a belgium company. > I have a question regarding cygwin and its use. > Is it allowed/legal to integrate cygwin installer (2.11.1(0.329/5/3)) into > the installer of an application that we plan to distribute commercially? > I have checked the past cygwin posts but I did not see any clear answer to > my question. > I know how to handle source code in LGPL but I have difficulty to > understand what I can do with cygwin (LGPL) but which also contains tools > covered by the GNU GPL and so on. > We have customized cygwin installer in order to install locally the > necessary packages. > Once in its execution, our application launches cygwin.bat and launch > commands to upload embedded systems. > We do not link towards cygwin.dll. cygwin1.dll > We currently use the application internally but we plan to distribute it > commerically in the future. > Thanks in advance for your support/feedback, [Disclaimer: I am not any kind of lawyer or project lead just another volunteer] Cygwin is not a formal organization and has no officers or lawyers, at best volunteer project co-leads and maintainers with commit privileges to primary source repositories. Cygwin is an online project which has volunteers around the world collaboratively maintaining a collection of packages archived and distributed on third party donated and supported domain names and infrastructure. Copyright and licence compliance is your responsibility if you download any binaries or sources. As you are based in Belgium in the EU you also have to comply with Belgian and EU law which may have stricter copyright and licensing compliance requirements. Each package comes with its own licensing terms, including cygwin (cygwin1.dll) and setup (setup_x86{_64}.exe), usually under (case insensitively): /usr/share/{,doc/}PACKAGE{,-doc}/*{COPY,LICEN}* or /usr/share/doc/common-licenses You will have to provide your corporate lawyers with the licences for each package you wish to include in your product. Your corporate lawyers will have to determine what responsibilities you have related to package licensing requirements, what you must do (e.g. publish and attribute all copyrights and licences in your product distribution and documentation, distribute and provide online source archives, and submit patches upstream, etc.), and how you are limited by the licences in what you may do with each package. As so many packages are licensed under the [L]GPL2/3 or by the FSF if GNU sourced, see https://www.fsf.org/licensing/ your corporate lawyers may want to work with the FSF Licensing and Compliance Team mailto:licensing@fsf.org or their lawyers mailto:legal@fsf.org as Cygwin has no lawyers. In general, you probably need to document, track, submit, and log submission of any modifications you make to any Cygwin package source code as patches to cygwin-apps@cygwin.com, or upstream to the upstream package maintainer or source given in the package source archive, often shown in a .cygport file. Question for project leads - who maintains the maintainer copyright assignments, attributions, disclaimers, releases, etc. and where, or is that all also only in some mail archives? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple