4 ms·
Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeW
by a3_nm 10y ago
Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeWeaver's fork of Wine was proprietary.
(Sources: https://en.wikipedia.org/wiki/Wine_(software)#History https://en.wikipedia.org/wiki/Wine_(software)#History https://www.winehq.org/pipermail/wine-devel/2002-February/003912.html https://www.winehq.org/pipermail/wine-devel/2002-February/00...)
CodeWeaver's Wine variant still seems to be proprietary according to Wikipedia -- I wonder what made the relationship between CodeWeavers and Wine evolve.
- bonzini 10y agoWhile there is some proprietary glue, all changes to the Wine code are (as they have to be) open source.
- mook 10y agoI believe it was actually that a different fork of Wine was not contributing back which caused the license change. I want to say it was Cedega but memories are hazy at this point (since I'm an outside observer).
- coldpie 10y agoCodeWeavers's usage of Wine and other open-source projects has always been open-source. You can download our Wine fork source from our website[1]. We do use a small amount of closed-source glue to provide our installation magic and desktop integration. Wine switched to LGPL due to other proprietary forks. [1] https://www.codeweavers.com/products/more-information/source https://www.codeweavers.com/products/more-information/source
- Fnoord 10y ago> Wine switched to LGPL due to other proprietary forks. Specifically, WineX aka Cedega