This is the mail archive of the
mailing list for the Cygwin project.
Re: About Cygwin license
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Armo Super <armosuper at yahoo dot co dot uk>
- Cc: cygwin at cygwin dot com
- Date: Thu, 11 Dec 2003 09:27:54 -0500 (EST)
- Subject: Re: About Cygwin license
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On Thu, 11 Dec 2003, Armo Super wrote:
> What do you think about next situation?
> I have made an software, that I'm going to sell.
> My software uses PostgreSql database system, witch is
> distributed under BSD license.
> If I want to get PostgreSql run in Windows
> environment, I need Cygwin.
> My software -(direct use)-> JDBC -(socket)->
> PostgreSql -(direct?)-> Cygwin
> And now, is there any resctrictions towards my
> software from GPL, becouse my software is not using
> Thank you
Disclaimer: <http://cygwin.com/acronyms/#GPL>, first definition. Having
asked this question on the Cygwin list, you're about to receive loads of
*personal* opinions from *non-lawyers*, so it's in your best interest to
contact a real lawyer.
That aside, and with the understanding that IANAL:
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...
Of course, <http://cygwin.com/acronyms/#YANALATEYHSMBSI>.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,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: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html