This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: About Cygwin license

On Thu, 11 Dec 2003, Hughes, Bill wrote:

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

With the disclaimer (which you snipped) that IANAL, and any opinion you'll
get is a personal one:
The GPL is viral, i.e., anything linked (even dynamically) to a GPL'd
library is itself GPL'd, *except* when the software so linked is
distributed under an open-source license.  Transitive linking is still
linking, AFAIK.  So, linking with cygwin1.dll doesn't make PostgreSQL
GPL'd, as BSD is an accepted open-source license.  But any proprietary
software linked to PostgreSQL (and, transitively, to cygwin1.dll) *will*,
IMO, become GPL'd.  Again, YANALATEYHSMBSI.  Please consult a lawyer.
      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]