From: DJ Delorie <dj@redhat.com>
To: neroden@twcny.rr.com
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Libiberty license roundup (questions/potential problems)
Date: Fri, 23 May 2003 23:06:00 -0000 [thread overview]
Message-ID: <200305232306.h4NN6Bh16936@greed.delorie.com> (raw)
In-Reply-To: <20030523225905.GA30461@doctormoo> (message from Nathanael Nerode on Fri, 23 May 2003 18:59:05 -0400)
> Looking at libiberty, it seems to be under a mass of different
> licences.
Yup. It will probably stay that way, too, because changing copyright
terms is *very* difficult.
> The fourth are the various files which aren't sure what they're part
> of; I'd like permission to just fix those all to claim to be part of
> libiberty, unless there's some reason not to.
The reason is, only the original author can change the copyright terms.
> The fifth is the question of why some are LGPL, some are GPL, some
> are GPL with linking exception, and one is LGPL with linking
> exception. Effectively the library as a whole is under GPL in
> general, it would seem; what purpose do the other licenses serve?
Some have the exception because they're used in libstdc++, for
example. There is no "library as a whole" as far as libiberty is
concerned; each source file has its own license, and that's pretty
much the end of the story, since there's little we can do about it.
next prev parent reply other threads:[~2003-05-23 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 22:59 Nathanael Nerode
2003-05-23 23:06 ` DJ Delorie [this message]
2003-05-23 23:59 ` Mike Stump
2003-05-24 1:23 ` Andrew Cagney
2003-05-24 1:34 ` DJ Delorie
2003-05-28 19:27 ` Andrew Cagney
2003-05-28 22:08 ` Joe Buck
2003-05-30 17:27 ` David O'Brien
2003-05-30 18:59 ` DJ Delorie
2003-05-28 22:11 Robert Dewar
2003-05-28 22:23 ` Joe Buck
2003-05-28 22:23 Robert Dewar
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=200305232306.h4NN6Bh16936@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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).