Re: Re (3): testing before a release

[Mark Wielaard]

Hi,

On Thu, Nov 08, 2001 at 07:38:15AM -0500, Brian Jones wrote:
> address@hidden writes:
> 
> > The fact it doesn't work yet is no excuse. It will work someday. And applets
> > use the AWT. Writing a VM that doesn't support applets makes no sense.
> > 
> > The VM loads the applets, and must (dynamically) link itself to those
> > classes and start their execution, so the VM has to use the applet class.
> > 
> > Etienne also had a good point about the Spec JVM benchmark. I had a quick
> > look at it:
> > * _202_jess imports the awt
> > * the whole suite must be run as an applet
> 
> Yes, to get around this issue for now run the individual parts by hand
> instead of through the applet.

There seems to be some misunderstanding here. Using and/or running Classpath
is never a problem (as long as you don't distribute the derived work).

I tried to send the following message, but used the wrong email address
so the mailinglist didn't accept it:

Just I quick note since I have no time at the moment to discuss this
in full length. When I have time I will try to finish the LICENSE
document that I started and will focus on the meaning of the
GPL+exception and just ignore the AWT+GPL thing for the moment.

Running a program is in no way restricted by the GPL only distribution
has to follow a few rules (mainly keep it Free and GPL compatible).
So you are free to download and use any GPLed program, build and run
any derived works as long as you don't distribute it. Only when
distributing a derived work based on a GPLed program or library
do the GPL terms come into effect.

See the GPL Faq for more information.
<http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic>

Cheers,

Mark

-- 
Stuff to read:
    <http://www.toad.com/gnu/whatswrong.html>
  What's Wrong with Copy Protection, by John Gilmore