javax.naming work (Classpath vs ClasspathX)

Sun Oct 21 23:48:00 GMT 2001

Mark Wielaard wrote:
>Also note that the GPL+exception does not make everyone feel that easy.
>Most people know the implications of the (L)GPL
>Many people think they know the implications of the LGPL. Even proprietary
code can link againt LGPL libraries - as long as the libraries are 
shared libraries.
However, linking against static libraries (as you might have to do on 
embedded
system or want to do on other systems to reduce librray version 
dependencies)
is in practice ruled out for non-Free software. Whether this is a 
problem depends
on your perspective. When I was at Cygnus (which was heavily dependent on
the embedded marketplace) this was a problem.
>but are not sure about
>the exact implications of the GPL+Exception. We might want to clearify
>the language at a later state.
>I don't diagree with that. However, GPL+Exception has been used for libgcc
(the gcc core library, not glibc) since the very early days of gcc.