From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: binutils@sourceware.org
Subject: libsim licensing (and bfd by extension)
Date: Tue, 04 May 2010 23:52:00 -0000 [thread overview]
Message-ID: <201005041952.22036.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
the current sim/ subdir lacks an upfront statement as to its licensing (which
is to say there is no COPYING file). some sim-subdirs even have their own
COPYING file. if we go by the source files, the overall license appears to be
GPL-3 (some are GPL-2+).
what i think would be nice is if the libsim interface was granted an exception
to be used under the LGPL-3. by itself, this wouldnt be of value because
libsim requires libbfd which is under the GPL-3. so there would need to be a
minor grant where libbfd would not incur GPL-3 on everything else when it is
being pulled in purely for libsim's needs. obviously this would not apply if
the code linking against libsim also used bfd symbols directly.
while libsim also uses libiberty, that is under LGPL-2.1, so that's done.
does this have any chance of happening ? or should i just say screw it and
post a toplevel sim/COPYING patch ;).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2010-05-04 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 23:52 Mike Frysinger [this message]
2010-05-05 3:12 ` Daniel Jacobowitz
2010-05-05 5:04 ` Mike Frysinger
2010-05-07 18:24 ` Robin Getz
2010-05-07 18:25 ` Daniel Jacobowitz
2010-05-07 19:39 ` Robin Getz
[not found] ` <201005071539.03142.rgetz__26985.0316843533$1273261162$gmane$org@blackfin.uclinux.org>
2010-05-08 16:54 ` Frank Ch. Eigler
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=201005041952.22036.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
/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