From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: License manifest OR handling
Date: Mon, 13 Oct 2014 16:17:52 -0500 [thread overview]
Message-ID: <543C4180.1050902@linux.intel.com> (raw)
Hi everybody,
I'm working in one bug [1] related to License manifest creation and i
have some concerns about what is
expected in License creation more specifically in the OR's handling.
I re-implemented license creation function from shell to python for use
oe.license module and added support
for take into account INCOMPATIBLE_LICENSES.
For example: Currently if you have LICENSE set to (MPLv2 | GPLv2.1) &
LGPLv3,
- With INCOMPATIBLE_LICENSES not set the result is: MPLv2 LGPLv3.
- With INCOMPATIBLE_LICENSES set to MPLv2 the result is: GPLv2.1
LGPLv3.
This is that oe.license model eval's the OR expression and if you have
several OR only one is chosen, this is
the expected behavior?, if yes i think is needed to add priorities for
license choose, example [2].
Comments?
Best regards.
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6765
[2] https://gist.github.com/kergoth/1590028
next reply other threads:[~2014-10-13 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 21:17 Aníbal Limón [this message]
2014-10-13 22:18 ` License manifest OR handling Jonathan Liu
2014-10-14 19:19 ` Aníbal Limón
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=543C4180.1050902@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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