From: Kevin Buettner <kevinb@redhat.com>
To: Bob Rossi <bob@brasko.net>, Alain Magloire <alain@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: libtgdb or libgdb
Date: Thu, 17 Jul 2003 21:35:00 -0000 [thread overview]
Message-ID: <1030717213551.ZM16697@localhost.localdomain> (raw)
In-Reply-To: Bob Rossi <bob@brasko.net> "Re: libtgdb or libgdb" (Jul 17, 4:49pm)
On Jul 17, 4:49pm, Bob Rossi wrote:
> Well, I am not sure about the license. To me, thats not really a big
> deal. It will defiantly be under the GPL, however, I don't know what to
> do with the copyright.
The license is a big deal. The license you choose will likely
determine how widely your library is used or even if it is used at
all.
> Is there any advantage to making it GPL and keeping the copyright or
> making it LGPL and giving the copyright to the FSF?
If you make the licesne GPL, but retain the copyright, you (and only
you) have the option of relicensing the software under other terms.
These terms might include payment of a fee to you in exchange for a
license which allows the library to be linked against proprietary
software.
If you assign the copyright to the FSF and also persuade the FSF to
license your library under the LGPL, then it will be possible for
non-free software to link against your library. However, given that
your library would provide a way for non-free software to use the
facilities available in GDB (which is GPL'd software in the GNU
project), the FSF might not be willing to accept your library.
> Would either of those scenarios effect companies?
Yes. Using the LGPL would allow proprietary software to be linked
against your library. Using the GPL would disallow this unless you
provide alternate licensing terms for proprietary software.
Kevin
next prev parent reply other threads:[~2003-07-17 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 2:34 Bob Rossi
2003-07-17 0:54 ` Bob Rossi
2003-07-17 15:35 ` Alain Magloire
2003-07-17 20:49 ` Bob Rossi
2003-07-17 21:35 ` Kevin Buettner [this message]
2003-07-11 11:29 Hassan Aurag
2003-07-11 23:55 ` 'Bob Rossi'
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=1030717213551.ZM16697@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=alain@qnx.com \
--cc=bob@brasko.net \
--cc=gdb@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