This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin for Government Use
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 31 Mar 2004 23:36:12 -0500
- Subject: Re: cygwin for Government Use
- References: <1FFD627BFDAEE0468AA006E0AD632470138E1D@uncl-mail.caa.army.mil> <20040331142404.GP17229@cygbert.vinschen.de> <406B995A.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot 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? -> email@example.com
Cygwin Project Co-Leader firstname.lastname@example.org
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html