From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30487 invoked by alias); 13 Feb 2002 19:25:10 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 30410 invoked from network); 13 Feb 2002 19:25:08 -0000 Received: from unknown (HELO PH01SRV02.photuris.com) (141.150.26.4) by sources.redhat.com with SMTP; 13 Feb 2002 19:25:08 -0000 Received: by PH01SRV02.photuris.com with Internet Mail Service (5.5.2653.19) id ; Wed, 13 Feb 2002 14:22:45 -0500 Message-ID: From: Doug Fraser To: Robert Hartley Cc: MDavies@uk.waukbearing.com, sourcenav@sources.redhat.com, 'Ian Roxborough' Subject: RE: SN backend GPL or LGPL? (was: SourceNav release...) Date: Wed, 13 Feb 2002 11:55:00 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-q1/txt/msg00069.txt.bz2 If you link in a library, your new work embodies that library, and thus is covered by the license of the underlying library. If that were not so, then any OpenSource project could be turned into a library in order to void the GPL. So the act of linking to a library binds your work to the underlying license. Deriving a library from a GPL product conveys GPL status to that library, since the library is a derivative work. Which, in the spirit of the tool and the spirit of OpenSource, is as it should be. However, I can't see that it would keep you from developing an extended IDE if the rest of the IDE communicated to SN through an API that did not require linking. CORBA as you say or a database. You could develop that API, feed it back to the community, then move forward with the proprietary tools, just using a separate SN as a backend. Some would argue against that on philosophical grounds, but it would appear to be quite legal. Personally, I am quite happy with my SN5.0 release. One of these days, work permitting (yeah, fat chance...) I want to learn how to hook it into the backend of VIM, so I can use VIM as my editor, and have it feed controls back to SN. VIM has a backend hook built into it, so it should not be too hard. Thank you to the all the fine folk who have provided and contributed to SN. Doug > -----Original Message----- > From: Ian Roxborough [mailto:irox@redhat.com] > Sent: Wednesday, February 13, 2002 1:40 PM > To: Robert Hartley > Cc: MDavies@uk.waukbearing.com; sourcenav@sources.redhat.com > Subject: Re: SN backend GPL or LGPL? (was: SourceNav release...) > > > On Wed, 13 Feb 2002 13:38:26 -0500 Robert Hartley > wrote: > > > > What I was trying to ask is if we made the back end of SN a > shared library, > > libSNdb.so, would every thing that linked to this library > have to be GPL'd or > > would the library be able to be treated as a LGPL work? > > This would require a change to the licensing, which probably > won't happen. > > Ian. >