From: Mark Wielaard <mark@klomp.org>
To: Elena Zannoni <elena.zannoni@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Disassembly source buffer and libopcodes
Date: Wed, 22 Aug 2007 14:51:00 -0000 [thread overview]
Message-ID: <1187794289.3759.20.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46CC476F.7000106@oracle.com>
Hi Elena,
On Wed, 2007-08-22 at 10:25 -0400, Elena Zannoni wrote:
> > Since Fedora did a license audit and found we were linking in libopcodes
> > from binutils which is under GPL, but we distribute Frysk under GPL +
> > Exception, automatic libopcode usage has been disabled (you need to
> > configure --with-libopcodes to get it).
>
> Thanks for discussing this on the mailing list, can you explain a bit
> more about it?
> I wasn't aware of the audit, is this a RH thing? or a fedora thing? Does
> it impact frysk in other ways?
It is a Fedora thing. They are cleaning up the package license tags:
http://fedoraproject.org/wiki/PackagingDrafts/LicenseTag
This means all packages are audited now. The main Frysk license is GPL +
Exception so we can link with non-gpl compatible code like eclipse. One
of the maintainers noticed that we were using binutils (libopcodes)
which is GPL-only though, so cannot be used in a larger work with EPL
code.
> I assume this is reason for the change Andrew made on
> August 16?
> http://sourceware.org/ml/frysk-cvs/2007-q3/msg00648.html
>
> Is there any public discussion of the audit?
fedora-devel and fedora-maintainers has lots, but those are super busy
lists: http://www.redhat.com/mailman/listinfo/fedora-devel-list
https://www.redhat.com/archives/fedora-maintainers/
This particular issue came up here first I believe:
https://www.redhat.com/archives/fedora-maintainers/2007-August/msg00264.html
Cheers,
Mark
next prev parent reply other threads:[~2007-08-22 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 12:26 Mark Wielaard
2007-08-22 14:27 ` Elena Zannoni
2007-08-22 14:51 ` Mark Wielaard [this message]
2007-08-22 16:02 ` Elena Zannoni
2007-08-22 18:13 ` Mark Wielaard
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=1187794289.3759.20.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=elena.zannoni@oracle.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).