From: Saul Wold <sgw@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: qemu-config & non-gplv3
Date: Thu, 19 May 2011 22:10:49 -0700 [thread overview]
Message-ID: <4DD5F7D9.6070103@linux.intel.com> (raw)
Richard,
I was reminded again about the need to do non-GPLv3 sooner and more
often. I ran that today for core-image-basic on x86 and found 3 issues,
first 2 were easy and will be in tonight's consolidated pull.
This issue again was with qemu-config dragging in GPLv3 licensed stuff
and thus not having dependencies met. I understand the need for those
packages in a development/debug environment, but we need a flexible way
to enable and disable that task.
I know the easy way would be to club it over the head and remove
qemu-config from qemu.inc's MACHINE_ESSENTIAL_EXTRA_RDEPENDS, but that's
not the correct way!
We can make it be MACHINE_EXTRA_RDEPENDS or maybe more flexibly an
IMAGE_FEATURE that can be disabled for minimal or non-GPLv3 builds.
Thoughts?
Thanks
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
reply other threads:[~2011-05-20 5:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DD5F7D9.6070103@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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