Exclude GPLv3 license in the baseline builds

1. Scope
Baselines have to be able to be built without GPLv3 licensed files and packages, this is a GENIVI requirement.

It is known that the current controls in place to exclude GPLv3 code from being included in a release are catching various packages.This ticket is intended to include the tasks required to investigate excluded packages and identify any changes needed to the baselines.

For each package there are recurring questions when reviewing its exclusion: is it important that it is kept in the baseline? Why is it included? What is the dependency tree that pulls it in?

2. Technical detail
In Yocto it is controlled by adding GPLv3 licenses to the INCOMPATIBLE_LICENSE variable of the local.conf

2.1 Yocto license mechanism
The Yocto Maintainer has reported the exclusions reported by Yocto when building the Genivi 11 M-1.0 release and excluding GPLv3, LGPLv3 and AGPLv3. See the attached log for the specific details:
README-result-of-build-with-LGPLv3-AGPLv3-inhibited.log

In summary they are:
libidn-1.33-r0: idn, libidn-dbg, libidn-staticdev, libidn-dev, libidn-doc
cairo-1.14.6-r1: cairo-dbg, cairo-staticdev, cairo-doc, cairo-locale
gnutls-3.5.3-r0: gnutls-openssl, gnutls-dbg, gnutls-staticdev, gnutls-dev, gnutls-doc, gnutls-bin
libgcrypt-1.7.3-r0: dumpsexp-dev, libgcrypt-dbg, libgcrypt-staticdev, libgcrypt-doc, libgcrypt-locale

2.2 LRT source scan
The LRT has also scanned the source and a report (attached) produced on the files with xGPL-3 licenses. Some of these relate to the packages identified above, some are not. The findings need to be investigated and any additional tasks identified.