RE: License question (Distribution of cygwin1.dll

patrick schmidt sent the following at Monday, May 07, 2018 10:28 AM > >I want to use iPerf3.exe in an commercial projekt. iPerf uses the MIT >License but needs cygwin1.dll in order to function correctly. > >I need to distribute iperf3.exe in our commercial software, but we cant >release the source

Re: License conflicts in Cygwin

On 02/24/2011 03:22 AM, Corinna Vinschen wrote: > Disclaimer: IANAL. I can't speak for our legal dept, of course. There > won't be any changes in the Cygwin license any time soon as far as I'm > aware. If your lawyers feel that they have more questions about this, > the best course of action mig

Re: License conflicts in Cygwin

On Feb 24 10:55, Denk, Uwe wrote: > Hello, > > we would like to use Cygwin. After checking the license conditions we > found two license conflicts in Cygwin, which is GPL v2 licensed in > accordance with the COPYING files of Cygwin: First of all, you're referring to an old version of Cygwin. Ri

Re: License violation: gpsd4win

On Jul 11 22:56, Yaakov S wrote: > http://code.google.com/p/gpsd-4-win/ > > This project provides an installer containing cygwin1.dll and at least a > Base installation. The project's SVN repo also contains the same > binaries. Nowhere are sources to Cygwin or any other package provided. Thank

Re: license violation

On Jun 12 22:49, Buchbinder, Barry (NIH/NIAID) [E] wrote: > I hope that it is appropriate to duplicate reports of license violations when > a lot o time has passed? (This was reported 4 years ago > .) No worries. > These guys are distribut

Re: License

Corinna wrote: If you distribute a Cygwin DLL binary, you must also provide the sources of the DLL. It's not enough to point to the Cygwin web page. For further details, see http://cygwin.com/licensing.html And also as I understand the GPL, you should together along with the source to the cygwin

Re: License

Giulio Ardoino schrieb: Corinna Vinschen wrote: If you distribute a Cygwin DLL binary, you must also provide the sources of the DLL. It's not enough to point to the Cygwin web page. For further details, see http://cygwin.com/licensing.html Thanks a lot Corinna. This means I'm allowed to distribut

Re: License

Igor Pechtchanski wrote: > IANAL, but the GPL does talk about linking as separate from invoking the > programs using fork/exec. In particular, the following two sections from > the GPL FAQ might be relevant: > and >

Re: License

On Thu, 26 Aug 2004, Giulio Ardoino wrote: > Corinna Vinschen wrote: > > > If you distribute a Cygwin DLL binary, you must also provide the > > sources of the DLL. It's not enough to point to the Cygwin web page. > > For further details, see http://cygwin.com/licensing.html > > Thanks a lot Corin

Re: License

On Aug 26 16:58, Giulio Ardoino wrote: > Corinna Vinschen wrote: > > > If you distribute a Cygwin DLL binary, you must also provide the sources > > of the DLL. It's not enough to point to the Cygwin web page. For further > > details, see http://cygwin.com/licensing.html > > Thanks a lot Corinna

Re: License

Corinna Vinschen wrote: > If you distribute a Cygwin DLL binary, you must also provide the sources > of the DLL. It's not enough to point to the Cygwin web page. For further > details, see http://cygwin.com/licensing.html Thanks a lot Corinna. This means I'm allowed to distribute cygwin dll as

Re: License

On Aug 26 16:25, Giulio Ardoino wrote: > Hello, > I have a question about cygwin license: > If I write a windows program that uses some tools contained in the > cygwin package (and therefore the dll itself), will I be able to > distribute my software with cygwin dll in it or do I have to post a > s

Re: License issue

On Wed, Jun 16, 2004 at 12:53:23PM -0400, Christopher Faylor wrote: > >I see. But I suppose, for an example described in > >http://cygwin.com/ml/cygwin/2004-06/msg00678.html , providing a piece of > >paper with such an offer in the product box should count as fulfilment > >of clause 3b? > So, basic

Re: License issue

On Wed, Jun 16, 2004 at 06:49:44PM +0300, Baurjan Ismagulov wrote: >On Wed, Jun 16, 2004 at 11:25:38AM -0400, Christopher Faylor wrote: >> The reason this doesn't count is not because we have an arbitrary restriction >> on the license. It is because it is extremely unlikely that you are going >> t

Re: License issue

Hello, Christopher! On Wed, Jun 16, 2004 at 11:25:38AM -0400, Christopher Faylor wrote: > The reason this doesn't count is not because we have an arbitrary restriction > on the license. It is because it is extremely unlikely that you are going > to send a postal mail offer to every person who acq

Re: License issue

On Wed, Jun 16, 2004 at 03:59:29PM +0300, Baurjan Ismagulov wrote: >On Wed, Jun 16, 2004 at 02:45:19PM +0200, Corinna Vinschen wrote: >> Huh? That's exactly section 3a, just take the "accompany" literally. > >Ok, thanks. > >> We don't distribute Cygwin under the 3b clause so that doesn't count >>

Re: License issue

On Wed, Jun 16, 2004 at 03:56:20PM +0200, Corinna Vinschen wrote: > What this company can not do is, to rely on Red Hat > to keep sources for three years and then point their customers to the > Red Hat web page. If they do, they are infringing the licensing. I see your point, thanks much for the

Re: License issue

On Jun 16 16:38, Baurjan Ismagulov wrote: > On Wed, Jun 16, 2004 at 03:10:48PM +0200, Corinna Vinschen wrote: > > > > We don't distribute Cygwin under the 3b clause so that doesn't count > > > > here at all. > > > This was my point. I couldn't find this on the web page; I'd like to see > > > it men

Re: License issue

On Wed, Jun 16, 2004 at 03:10:48PM +0200, Corinna Vinschen wrote: > > > We don't distribute Cygwin under the 3b clause so that doesn't count > > > here at all. > > This was my point. I couldn't find this on the web page; I'd like to see > > it mentioned (please point me to the text if I overlooked

Re: License issue

On Jun 16 15:59, Baurjan Ismagulov wrote: > On Wed, Jun 16, 2004 at 02:45:19PM +0200, Corinna Vinschen wrote: > > We don't distribute Cygwin under the 3b clause so that doesn't count > > here at all. > > This was my point. I couldn't find this on the web page; I'd like to see > it mentioned (pleas

Re: License issue

On Wed, Jun 16, 2004 at 02:45:19PM +0200, Corinna Vinschen wrote: > Huh? That's exactly section 3a, just take the "accompany" literally. Ok, thanks. > We don't distribute Cygwin under the 3b clause so that doesn't count > here at all. This was my point. I couldn't find this on the web page; I'

Re: License issue

On Jun 16 15:11, Baurjan Ismagulov wrote: > Hello, Corinna! > > On Wed, Jun 16, 2004 at 01:11:52PM +0200, Corinna Vinschen wrote: > > If you don't provide the sources on the same medium as the binaries, > > you're infringing the Cygwin license. > > I couldn't find this information (about the same

Re: License issue

Hello, Corinna! On Wed, Jun 16, 2004 at 01:11:52PM +0200, Corinna Vinschen wrote: > If you don't provide the sources on the same medium as the binaries, > you're infringing the Cygwin license. I couldn't find this information (about the same medium) on http://cygwin.com/licensing.html. IANAL, but

Re: License issue

On Jun 16 13:36, Jani tiainen wrote: > Corinna Vinschen wrote: > >On Jun 15 13:51, Avraham H. Fraenkel wrote: > >>If I am writing a short C program, comply it with GCC, and put the exe > >>and the cygwin dll in my site, should I add something? > > > >Yes, the sources of your application as well as

Re: License issue

Corinna Vinschen wrote: On Jun 15 13:51, Avraham H. Fraenkel wrote: If I am writing a short C program, comply it with GCC, and put the exe and the cygwin dll in my site, should I add something? Yes, the sources of your application as well as the sources of the Cygwin DLL, according to the GPL. I

Re: License issue

On Jun 15 13:51, Avraham H. Fraenkel wrote: > If I am writing a short C program, comply it with GCC, and put the exe and the > cygwin dll in my site, should I add something? Yes, the sources of your application as well as the sources of the Cygwin DLL, according to the GPL. If you don't distribu

Re: license for X-startup-scripts package

We have a mailing list for cygwin-x. Redirecting there. On Tue, Mar 23, 2004 at 03:02:23PM -0500, Dick Repasky wrote: >I'm looking for the license under which the X-startup-scripts package is >released. The file named COPYING is 1 byte long in >usr/X11R6/share/doc/X-startup-scripts-1.0.2/COPYI

Re: License question about cygwin

On Wed, Jul 16, 2003 at 02:48:14PM -0400, Tillman, James wrote: > > >> -Original Message- >> From: Elfyn McBratney [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, July 16, 2003 11:43 AM >> To: [EMAIL PROTECTED] >> Cc: Cary Lewis >> Subject: Re: Licen

Re: License question about cygwin

On Wed, Jul 16, 2003 at 04:46:24PM -0400, Bill C Riemers wrote: >The answer isn't quite that simple. The correct answer, is that it depends >on the details of what you are doing. I could go into more details, but >this topic has already been moderated once. It would be inappropriate for >me to d

Re: License question about Cygwin

> > As the Cygwin.dll is licensed under GPL, any "Program" that links to it must > > be released under GPL as well. > > Under section 10 of the GPL, if the "program" is OSD compatible then the > "program" is not auto-GPL'd. Actually section 10 of the GPL just states the following: > 10. If you wi

RE: License question about Cygwin

> -Original Message- > From: Elfyn McBratney [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 16, 2003 11:43 AM > To: [EMAIL PROTECTED] > Cc: Cary Lewis > Subject: Re: License question about Cygwin > > > On Wed, 16 Jul 2003, Elfyn McBratney wrote: >

Re: License question about Cygwin

RedHat has granted a special exception that allows any open source to link to Cygwin.dll. As the legal copyright holder, RedHat may grant any sort of exception to the GPL they want, and are not bound to the GPL. (This only applies to Cygwin.dll and other components that RedHat can claim ownershi

Re: License question about Cygwin

On Wed, 16 Jul 2003, Elfyn McBratney wrote: > On Wed, 16 Jul 2003, Cary Lewis wrote: > > > As the Cygwin.dll is licensed under GPL, any "Program" that links to it must > > be released under GPL as well. > > Under section 10 of the GPL, if the "program" is OSD compatible then the > "program" is not

Re: License question about Cygwin

On Wed, 16 Jul 2003, Cary Lewis wrote: > As the Cygwin.dll is licensed under GPL, any "Program" that links to it must > be released under GPL as well. Under section 10 of the GPL, if the "program" is OSD compatible then the "program" is not auto-GPL'd. > My question is, what if the "Program" als

RE: License question

: [EMAIL PROTECTED] Subject: Re: License question On Mon, Mar 10, 2003 at 10:04:01PM -0800, Pete Nordquist wrote: >Thank you, Christopher, for your quick reply. I didn't mean to imply >that every binary produced by gcc is GPLed. I'm not sure how you could take your assertion any othe

Re: License question

On Mon, Mar 10, 2003 at 10:04:01PM -0800, Pete Nordquist wrote: >Thank you, Christopher, for your quick reply. I didn't mean to imply >that every binary produced by gcc is GPLed. I'm not sure how you could take your assertion any other way unless you think there is something special about cygwin

RE: License question

ter Science Southern Oregon University [EMAIL PROTECTED] 541/552-6148 -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2003 8:43 PM To: [EMAIL PROTECTED] Subject: Re: License question On Sun, Mar 09, 2003 at 06:47:44PM -0800, Pete Nordquis

Re: License question

On Sun, Mar 09, 2003 at 06:47:44PM -0800, Pete Nordquist wrote: >I read the following on >http://sources.redhat.com/cygwin/faq/faq_1.html#SEC4 > >In particular, if you intend to port a proprietary (non-GPL'd) >application using Cygwin, you will need the proprietary-use license for >the Cygwin libra