[poky] Miss-match between excluded license names and license name files
Andrei Gherzan
andrei at gherzan.ro
Sun Jan 8 04:32:57 PST 2012
Hello all,
I faced another GPLv3 related bug/issue. This one goes like this. In
base.class excluded/skipped packages from build are those that are
EXACTLY as they are typed in INCOMPATIBLE_LICENSE. For example a package
with LICENSE=GPLv3 will be excluded from build and one with
LICENSE=GPL-3 won't be. That would be a problem because a package like
gettext 0.18 where LICENSE=GPL-3 is not excluded even if it is GPLv3.
The standard license name for versions of GPL is indeed GPL-X.Y. Example
GPL-3.0. So, as i see we have a couple (2) of fixes for this.
1. Modify gettext's LICENSE to GPLv3. This is the quick one but no so...
let's say standardized. I will commit this change as a workaround (or
not) until we will have a conclusion upon this matter.
2. Recode base.bbclass part where INCOMPATIBLE_LICENSE is managed in
order to take into consideration those license variations defined in
license.bbclass. This is the "long" fix. An issue here would be that all
mapping in license.bbclass is on GPL-3.0 (as i think should be in this
naming standard). So we will have to redefine INCOMPATIBLE_LICENSE to
this value after the base.bbclass specified recoding is done. In this
way all those workarounds with "if GPLv3 is in INCOMPATIBLE_LICENSE"
will have to be modified as well, to check for GPL-3.0. In this way we
can take advantage of the already done mapping in license.bbclass, let
developers have their variations of LICENSE and still skipping those
packages from non-GPL-3.0 license builds. I think that this would be the
most complete fix in order to scale this INCOMPATIBLE_LICENSE issue.
Andrei
More information about the poky
mailing list