[oe] [meta-oe][PATCH 0/3] Add CVE_PRODUCT fields to a few recipes

[Mikko Rapeli]

This way yocto cve-check can find open CVE's for these recipes. See also:

http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139897.html

"Results from cve-check are not very good at the moment.
One of the reasons for this is that component names used in CVE
database differ from yocto recipe names. This series fixes several
of those name mapping problems by setting the CVE_PRODUCT correctly
in the recipes. To check this mapping with after a build, I'm exporting
LICENSE and CVE_PRODUCT variables to buildhistory for recipes and
packages."

Mikko Rapeli (3):
  fribidi_0.19.7.bb: set CVE_PRODUCT to gnu_fribidi
  krb5_1.15.1.bb: set CVE_PRODUCT to kerberos
  udisks2_2.1.8.bb: set CVE_PRODUCT to udisks

 meta-oe/recipes-connectivity/krb5/krb5_1.15.1.bb      | 2 ++
 meta-oe/recipes-devtools/libfribidi/fribidi_0.19.7.bb | 2 ++
 meta-oe/recipes-support/udisks/udisks2_2.1.8.bb       | 2 ++
 3 files changed, 6 insertions(+)

-- 
1.9.1