public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Robert Hartley <rhartley@ics.com>
To: "Davies, Mike" <MDavies@uk.waukbearing.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: SN backend GPL or LGPL?  (was: SourceNav release...)
Date: Wed, 13 Feb 2002 10:50:00 -0000	[thread overview]
Message-ID: <3C6AB2A2.5121A504@ics.com> (raw)
In-Reply-To: <50D13214B9CBD41180800008C7CFB62C45F4D5@AZTEC>

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

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?

Ian?

-rob

"Davies, Mike" wrote:

> > What if we had some sort of Corba type middle ware that provided a
> > decent distributed API, without actually linking the code in.
> >  Would any
> > application that connected to it still be bound by the GPL?
>
> Any changes you made to the Sourcenav Code would be GPLed and you would have
> to provide them in the usual ways,  however it seems to me that any
> application that used the CORBA interface would be effectively dynamically
> linked to it and so might escape the GPL.
>
> > I am trying to find out here if there is any room for commercial
> > developers to contribute to SN.  It would be a shame to let
> > it all go to
> > waste.
>
> Well,  many commercial firms contribute to GPLed SW,  there is nothing
> stopping you from doing that.  If you are trying to make a proprietry
> version of SourceNav then this is prohibited by the licence.  That is quite
> apart from the implications for the feelings of people who contributed their
> efforts freely for the common good.
>
> Mike Davies

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

begin:vcard 
n:Hartley;Robert
tel;fax:617-621-9555
tel;work:617-621-0060
x-mozilla-html:TRUE
url:http://www.ics.com/
org:Integrated Computer Solutions (ICS);Engineering
version:2.1
email;internet:robert.hartley@ics.com
title:Systems Engineer
adr;quoted-printable:;;Sixth Floor=0D=0A201 Broadway;Cambridge;MA;02139;USA
x-mozilla-cpt:;7328
fn:Robert Hartley
end:vcard

  reply	other threads:[~2002-02-13 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 10:38 Davies, Mike
2002-02-13 10:50 ` Robert Hartley [this message]
2002-02-13 11:25   ` Ian Roxborough
  -- strict thread matches above, loose matches on Subject: below --
2002-02-15  9:43 Doug Fraser
2002-02-13 11:55 Doug Fraser
2002-02-13 12:49 ` Robert Hartley
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=3C6AB2A2.5121A504@ics.com \
    --to=rhartley@ics.com \
    --cc=MDavies@uk.waukbearing.com \
    --cc=sourcenav@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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