From:	jqb AT netcom DOT com (Jim Balter)
Subject:	Re: Commercial Licensing
30 Mar 1997 21:55:48 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<333F41C6.5977.cygnus.gnu-win32@netcom.com>
References:	<3 DOT 0 DOT 32 DOT 19970330203114 DOT 011d24a0 AT reedkotler DOT com>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (WinNT; I)
Original-To:	Reed Kotler Consulting <reed AT reedkotler DOT com>
Original-CC:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Reed Kotler Consulting wrote:

> I suppose thought that you could relink cygwin.dll adding those other
> components and then you wouldnt be violating any rules.

libccrt0 has to live in the .exe, not the dll.  If Cygnus had published
an interface specification for cygwin.dll then of course you could
just say that you were following the spec if you provided your own
version, but they haven't.  As I said, I don't know how copyright
law applies to reverse engineering.

> In that case you could distribute your own version of cygwin.dll,
> under GPL of course and then you would not be linking in any code
> from cygwin.dll.

Distributing a modified cygwin.dll or putting it at an ftp site
separately from that which depends on it is really pushing things, and
seems pretty dangerous if anyone actually brought suit.

> However, presumably cygnus can't enforce GPL anyway, only FSF can do
> that.

Huh?  The copyright on libcygwin.a and cygwin.dll belong to Cygnus
Solutions, not the FSF; the FSF just publishes the text of copyright,
but that doesn't give them any legal standing.  And it's the courts that
enforce these things.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -