Tzafrir Cohen wrote:
On Mon, 23 Dec 2002, Hetz Ben-Hamo wrote:Wine is composed of two main parts (well, three, but let that be). The first is a loader capable of performing the dynamic linking necessary in order to load Dos, Win16 and Win32 binaries. The second is a bunch of DLLs implementing a bunch of functions, that happen to match a bunch of DLLs and a bunch of functions a company by the name of Microsoft (tm) wrote. Both parts are released under the LGPL. (The third part, if anyone is interested, is a 100% native program that gives services to the DLLs for services that cannot be implemented using other Win32 services).
So: is wine really LGPL-ed?
How come a propriertary piece of code be part of that product? Is that a
separate binary? a special clause in the license?
As a result, I can enhance Wine's compatibility, under certain circumstances, without modifying the wine source code (or, for that matter, even having the sources, just like some Windows programs do). That is what CW claim XOO is doing.
Now, I'm not sure how you can do some of these things and accomplish what they do, but there is a perfectly simple way in which Hetz or Daniel or anyone else who has bought XOO can verify that. Simply compile wine from the sources and replace the XOO binaries with the cooresponding binaries from your compile. If everything continues to work as it did before, probably no LGPL violation, and everyone should be happy.
("won't make any money" is a moral justification, but still does not makeTrue enough.
anything legal)
Shachar
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
