----- Original Message -----
> From: Earnie Boyd <earnie@...>
> To: MinGW Users List <mingw-users@...>
> Sent: Friday, 16 November 2012 6:29 PM
> Subject: Re: [Mingw-users] Msys licensing terms
> On Thu, Nov 15, 2012 at 10:19 PM, Nathan Ridge wrote:
>>> > Thanks. Is there any way enterprise can buy out the license?
>>> That depends on the licensor and the copyright holder. You have to
>>> read the license material to determine that. Since we (mingw.org) own
>>> none of the copyrights for MSYS, GCC, etc then we cannot grant you the
>>> privilege to do that.
>> Out of curiosity, who does own the copyrights for MSYS?
> The canonical place for the copyright holder is within the source that
> is copyrighted. MSYS was a fork of Cygwin and the winsup/cygwin
> directory of the source is what contains code specific to Cygwin.
> That code source was first copyrighted by Cygnus which was purchased
> by Redhat; therefore Redhat owns the copyright. Redhat does offer a
> proprietary version of Cygwin for which you can pay to have the GPL
> copyleft removed; but that doesn't extend to MSYS.
Since this is a fork of cygwin, I presume most of the packages in MSYS are covered under GPL? Is that correct?
>> 3. A file named 'CYGWIN_LICENSE' which says that "this
>> (without saying exactly what program) is distributed under the GPL,
>> with an exception under section 10. The file gives contact info
>> for 'Cygnus Solutions', but does not claim that Cygnus Solutions
>> owns the copyright for anything in this package.
> A license to use isn't a copyright statement. The copyright belongs
> with the source that is being copyrighted. The GPL offers you the
> benefit of applying an exception to the GPL. The CYGWIN_LICENSE file
> was the original LICENSE file that I copied at the time of the fork.
>> 4. A file named 'MSYS_LICENSE.rtf' which contains a statement
>> "Earnie" (I assume that's you, but the presence of a last
>> may have been helpful) that makes statements such as "MSYS contains
>> several different other packages" and "you may redistribute
>> in part or in whole as long as you follow the guidelines of
>> redistribution of each license contained within". It does not say
>> what these other packages are , who their copyright holders are,
>> whether there is a component of MSYS other than these "other
>> packages" (I assumed that was msysCORE was), and if so who owns
>> the copyright to this component.
> Any GPL source that is modified allows me to copyright the source of
> the modification. The MSYS_LICENSE document was an attempt to help
> clarify that MSYS was a bundling of disparate sources each having
> their own license and copyright holders.
>> To be honest, looking at these files left me utterly confused as to
>> who owns the coyprights to MSYS and how it's licensed.
> Because you weren't looking at the copyright information by looking at
> the license files.
> -- https://sites.google.com/site/earnieboyd
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> MinGW-users mailing list
> This list observes the Etiquette found at
> We ask that you be polite and do the same. Disregard for the list etiquette may
> cause your account to be moderated.
> You may change your MinGW Account Options or unsubscribe at:
> Also: mailto:mingw-users-request@...