From: Rotter Klaus <Klaus.Rotter@erl9.siemens.de>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>,
Simon Crase <tangaroa@mira.net>
Subject: AW: Distributing cygwin1.dll
Date: Tue, 31 Aug 1999 00:11:00 -0000 [thread overview]
Message-ID: <1B6FF887D79FD2119FDB00805FBED48B01C129BA@erlm511a.erl9.siemens.de> (raw)
Chris Faylor wrote:
>>Does the GPL really oblige me to make the source to the Cygnus tools
>>available on my site - which isn't even up yet :-( - in order for me to
>>distribute cygwin1.dll?
>
>Unfortunately, the licensing of the Cygwin DLL does require this. If you
If I understand the GPL right, someone don't have to publish the source, instead
if anyone requests the source, he has to give it away. This may include
sending the sources on CD-ROM and getting a copy fee. So I think there is no
problem just releasing your program in binary and only providing the source
for the program, not for the library.
But this is only true if cygwin.dll is under GPL. Maybe cygnus used a modified one.
--
Klaus Rotter, Siemens AG, ATD TD 6 EPG, Postfach 3249, 91020 Erlangen
Frauenauracherstraße 98, 91056 Erlangen
Tel.: +49 9131 18-84637, Fax: +49 9131 18-84648
mailto:Klaus.Rotter@erl9.siemens.de
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Rotter Klaus <Klaus.Rotter@erl9.siemens.de>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>,
Simon Crase <tangaroa@mira.net>
Subject: AW: Distributing cygwin1.dll
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <1B6FF887D79FD2119FDB00805FBED48B01C129BA@erlm511a.erl9.siemens.de> (raw)
Message-ID: <19990831234900.1H4aJvNXZQbxzfM_qzpRIFeZsPSsd7Z-Th823QhH70s@z> (raw)
Chris Faylor wrote:
>>Does the GPL really oblige me to make the source to the Cygnus tools
>>available on my site - which isn't even up yet :-( - in order for me to
>>distribute cygwin1.dll?
>
>Unfortunately, the licensing of the Cygwin DLL does require this. If you
If I understand the GPL right, someone don't have to publish the source, instead
if anyone requests the source, he has to give it away. This may include
sending the sources on CD-ROM and getting a copy fee. So I think there is no
problem just releasing your program in binary and only providing the source
for the program, not for the library.
But this is only true if cygwin.dll is under GPL. Maybe cygnus used a modified one.
--
Klaus Rotter, Siemens AG, ATD TD 6 EPG, Postfach 3249, 91020 Erlangen
Frauenauracherstraße 98, 91056 Erlangen
Tel.: +49 9131 18-84637, Fax: +49 9131 18-84648
mailto:Klaus.Rotter@erl9.siemens.de
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-08-31 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-31 0:11 Rotter Klaus [this message]
1999-08-31 15:14 ` Chris Faylor
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` AW: " Rotter Klaus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1B6FF887D79FD2119FDB00805FBED48B01C129BA@erlm511a.erl9.siemens.de \
--to=klaus.rotter@erl9.siemens.de \
--cc=cygwin@sourceware.cygnus.com \
--cc=tangaroa@mira.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).