In the unix community, there is a long lasting example on this: Netscape
(3.x, 4.x) is not gpl. Several (if not all) unix variants include the
movemail functionallity. THerefor it relies on the movemail package, which
is gpl.

With every netscape distribution that includes this movemail functionallity,
you receive a copy of the gpl and the movemail sources, just as the gpl
requires. This is the movemail source, exactly as it is used in netscape. I
don't know if it has been modifyed by Netscape but if so, the modifications
are in the distributed source.

See also some remarks below...

CBee.

--
C. Beerse
mailto:[EMAIL PROTECTED]
talkto:+31(71)5256660


> -----Original Message-----
> From: Alex K. Angelopoulos [mailto:[EMAIL PROTECTED]]
> There are a few takes on this, Ted - and I think you're 
> fairly free in this
> sense.  One minor quibble - GPL software is definitely not 
> public domain.  The
> difference from NASA's policy perspective may not matter, but from the
> standpoint of the GPL and what its intent is, it's a 
> completely different story,
> which actually helps you somewhat.

In short (how I remember it): GPL, copyleft and what ever nice name it has
just gives the copyright to the public, al the public and nothing but the
public.

> 
> (1) There are some people who have developed applications 
> that depend on VNC for
> key functionality which they sell commercially and do not 
> share the source code
> for - and they have not yet been sued...

My 2 cents:
If you start developing from scratch and use the gpl'd stuff (vnc) just as a
library or include stuff, just do so. Once you distribute your stuff, either
include the gpl'd stuff including it's source as the gpl says. Or use some
dynamically linking kind of thing, distribute without the glp'd stuff and
point your uses to get vnc themself.

If you start hacking the gpl'd source and end up having a totally different
tool, then I'd regard this as modifications to the source and you have to
follow the gpl for all you deliver: include source with it to the public of
your code.

An example of this: Oracle is available for linux. Linux is gpl. You either
get linux yourself and put Oracle on top of it or get oracle including linux
from your reseller. In both cases you end up with linux source and without
oralce source.

> 
> (2) There is no requirement in the GPL that you make your 
> source code for any
> mod available to the world - simply that when you distribute 
> software you also
> allow access to the source code to those to whom it is 
> redistributed, and that
> you do not impose additional restrictions on 
> redistribution(if my readings of
> the GPL are remembered clearly).

You can put any copyright of your choice on your code. GPL'd stuff will stay
gpl'd, including your mofifications.






CBee.
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to