Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<5D60432AF619D81183C80002A5419F5D07F532@nnhmsw1.cox.co.uk>
From:	"Hughes, Bill" <Bill DOT Hughes AT cox DOT co DOT uk>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: About Cygwin license
Date:	Thu, 11 Dec 2003 14:46:03 -0000
MIME-Version:	1.0

Sent: 11 December 2003 14:28 From: Igor Pechtchanski
> Common sense dictates that socket connections cannot be thought of as
> "linking" (which is what the GPL covers).  After all, connecting with a
> proprietary ssh client to a GPL'd ssh daemon on Linux doesn't make the
> client GPL'd (AFAIK).  Now, if your program is actually linked to some of
> PostgreSQL DLLs, that's a whole different story...
Isn't PostgreSQL under a BSD license anyway so that wouldn't be a worry
either...
unless this is a Cygwin dll for PostgreSQL?

--
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/

- Raw text -