Stephen Lau wrote: > Congratulations. You win the award for most useless comment ever. > Thanks for contributing. > > -steve > > James Cornell wrote: >> Wahh wahhh GPL wahh... >> >> James >> On May 28, 2008, at 9:39 AM, Bob Friesenhahn wrote: >> >> >>> On Wed, 28 May 2008, Ch? Kristo wrote: >>> >>>> Resources: >>>> Blastwave wine: http://www.blastwave.org/wine/ >>>> >>> Someone needs to inform the (unidentified) maintainer of Blastwave >>> wine that he is violating Wine's GPL license by not providing the >>> Wine source code used to build the binaries he offers for download. >>> Offering patches against some old Wine source code which is (or is >>> not) available from some other site is not sufficient to satisfy >>> GPL. If this is not fixed soon, then Blastwave should simply remove >>> the 'wine' section since surely Blastwave does not want to >>> intentionally violate open source licenses. This section is quite >>> an embarrassment to Blastwave and casts a shadow on the entire >>> project. >>> >>> I noticed this deficiency a while back when I wanted to build Wine >>> on Solaris. It made me rather angry since the source code the >>> patches are supposed to apply to is very old and difficult (if not >>> impossible) to find. >>> >>> Bob >>> ====================================== >>> Bob Friesenhahn >>> bfriesen at simple.dallas.tx.us, >>> http://www.simplesystems.org/users/bfriesen/ >>> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ >>> _______________________________________________ >>> desktop-discuss mailing list >>> desktop-discuss at opensolaris.org >>> >> >> _______________________________________________ >> desktop-discuss mailing list >> desktop-discuss at opensolaris.org >> > > Thanks Steve, *rolleyes* though I'm sure that such an award could never be made. Now, as someone has already said, Wine is under LGPL not GPL, there might be a few forks to pure GPLv2 (No one's really going V3, some are leaving the option open, Samba's probably the only big one planning and implementing)
I would definitely like to see a project and community around this nonetheless. Basic support from Codeweavers gurus would also definitely be nice, they don't have to go out of their way and quickly make work, but I definitely think they know the Wine internals as well as any. Transgaming's staff is too closed-minded and their fork is probably quite different in architecture as they implement caching mechanisms everywhere to deal with JIT-esc overhead. The patches are rolled into each release as far as I know. James
