Re: [Classpathx-javamail] LGPL replaced by GPL-with-exception

[Nic]

"Doug Porter" <address@hidden> writes:

> > The difference is that the gpl+exception allows linking the code to
> > non-gpl. But the source is protected.
> 
> Ok. That's simple and clear. And obviously I can't do anything else that
> might violate GPL along the way.

That's right.


> On the GNU Classpath page at http://www.gnu.org/software/classpath/ it
> talks about "core class libraries", but the exception itself doesn't use
> that language. Any idea what the page is talking about?

The page says this:

        "As such, it can be used to run, create and distribute a large
        class of applications and applets. When GNU Classpath is used
        unmodified as the core class library for a virtual machine,
        compiler for the java languge, or for a program written in the
        java programming language it does not affect the licensing for
        distributing those programs directly."

This is unhelpfull clarification  /8->

What they mean by this is: 

        if you're, say, a VM maker you can compile the unmodified
        Classpath source code and link that against your commerical VM
        product. If you modify the Classpath source code then "BAM"
        you're into GPL territory.


> And is there anything else I need to know, such as risks?

I don't think there are any risks associated with licencing your code
like this.

The biggest risk is that you still have the (C) to these classes so
you are legally responsible for ensuring that you have complied with
all the normal procedures regarding hacking Classpath or ClasspathX
code:

- you haven't seen the Sun source code

- you are free to write GPLed software 


Nic