You appear to be technically right, based on this. I remember reading the Cygwin license several years ago and concluding that I couldn’t use it at work; now I can’t remember if that was because of the GPL.
In practice, you can rarely use GPLed software libraries for development unless you work for a nonprofit. Cygwin is not a library, so you can use it as an operating system with no restrictions. I can’t remember now why I was so worried about they licensing terms. Perhaps they were different then.
That seems to overstate it rather—it’s a generalisation, but it’s mostly true. Most software written for for-profit employers isn’t GPL, and is often distributed even if only to a client or to other employees, so can’t link to GPLed libraries directly. Still that’s a long way from saying you can’t use Cygwin at work. Sebastian Hagen’s comment seems accurate to me.
You appear to be technically right, based on this. I remember reading the Cygwin license several years ago and concluding that I couldn’t use it at work; now I can’t remember if that was because of the GPL.
In practice, you can rarely use GPLed software libraries for development unless you work for a nonprofit. Cygwin is not a library, so you can use it as an operating system with no restrictions. I can’t remember now why I was so worried about they licensing terms. Perhaps they were different then.
That’s a gross overgeneralization.
That seems to overstate it rather—it’s a generalisation, but it’s mostly true. Most software written for for-profit employers isn’t GPL, and is often distributed even if only to a client or to other employees, so can’t link to GPLed libraries directly. Still that’s a long way from saying you can’t use Cygwin at work. Sebastian Hagen’s comment seems accurate to me.
Distributing to fellow employees is still internal to the company, is it not? So that would not trigger the public source clause.