Could someone explain the intent here, if not the motivation? If I package
a compiled version of the AWT in a dynamic library, I can presumably still
ship it with a proprietary application? If I link it in statically, the
whole program must be covered by the GPL? If I use any part of the library
other than the AWT, I'm fine either way?
Hans
-----Original Message-----
From: Tom Tromey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 07, 2000 9:18 AM
To: John Keiser
Cc: [EMAIL PROTECTED]; Java Discuss List; Classpath Project
Subject: RE: libgcj / Classpath relicensing and cooperation
>>>>> "John" == John Keiser <[EMAIL PROTECTED]> writes:
John> Could somebody *please* speak up and say what the heck is the
John> deal with the AWT? I do not remember ever hearing an
John> explanation of that nonsense. Is there reasoning behind it?
John> Perhaps because of the licensing of the native peers?
Stallman was adamant that AWT not be relicensed under more liberal
terms. It doesn't have anything to do with the native peers. You'll
have to ask him if you want more details.
Tom
