public inbox for
 help / color / mirror / Atom feed
From: Robert Hartley <>
Subject: Re: SN backend GPL or LGPL?  (was: SourceNav release...)
Date: Wed, 13 Feb 2002 12:49:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

Doug Fraser wrote:

> 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.

All other issues aside, using Corba or something as a workaround would not be
in the collaborative spirit of open source.

That is why I am wondering about an LGPL version of the SN backend.

Thanks to all for listening,

- Rob

[-- Attachment #2: Card for Robert Hartley --]
[-- Type: text/x-vcard, Size: 366 bytes --]

org:Integrated Computer Solutions (ICS);Engineering
title:Systems Engineer
adr;quoted-printable:;;Sixth Floor=0D=0A201 Broadway;Cambridge;MA;02139;USA
fn:Robert Hartley

  reply	other threads:[~2002-02-13 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 11:55 Doug Fraser
2002-02-13 12:49 ` Robert Hartley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-15  9:43 Doug Fraser
2002-02-13 10:38 Davies, Mike
2002-02-13 10:50 ` Robert Hartley
2002-02-13 11:25   ` Ian Roxborough
2002-02-13  9:06 Robert Hartley
2002-02-13 12:19 ` Syd Polk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).