Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 31 Mar 2004 23:36:12 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin for Government Use Message-ID: <20040401043612.GA6961@coc.bosbc.com> Mail-Followup-To: cygwin@cygwin.com References: <1FFD627BFDAEE0468AA006E0AD632470138E1D@uncl-mail.caa.army.mil> <20040331142404.GP17229@cygbert.vinschen.de> <406B995A.5080503@x-ray.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <406B995A.5080503@x-ray.at> User-Agent: Mutt/1.4.1i Reply-To: cygwin@cygwin.com On Thu, Apr 01, 2004 at 05:23:54AM +0100, Reini Urban wrote: >Corinna Vinschen schrieb: >>when reading http://cygwin.com/licensing.html, you will find that the >>licensing of Cygwin is pretty clear. >> >>Cygwin is Open Source, provided under the GNU Public License. >> >>That means basically, that all software linked against the Cygwin library >>is automatically Open Source as well. >> >>Two exception from this rule exist: >> >>- If your applications linked against the Cygwin library are only used >> for youyr own internal purposes, you don't have to make the sources >> public as well. > >Well, what about the poor internal guys using it? To my understanding >these internal guys must get access to the sources as well, even if >it's a closed community. Why not bolster your understanding with a refreshing read of the documentation available at the GNU web site? For instance: http://www.gnu.org/licenses/gpl-faq.html#InternalDistribution -- Christopher Faylor spammer? -> aaaspma@sourceware.org Cygwin Project Co-Leader aaaspam@duffek.org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/