once again into the code base i'm poring over, and this time, it's
about defining proprietary licenses for internal recipes.
turns out the meta-boundary layer has a nice example of what i'm
sure is the right way to do this (i've rarely had to do this myself),
wherein the layer's "layer.conf" file defines where to go get some
extra licenses:
LICENSE_PATH += "${LAYERDIR}/licenses"
or possibly some variant like (for ubiquitous acme corp.):
LICENSE_PATH += "${LAYERDIR}/files/acme-licenses"
to pair up with OE's .../files/common-licenses, you get the idea.
so i was puzzled when i saw all these clearly proprietary recipes
that did not define LICENSE or LIC_FILES_CHKSUM values but, instead,
inherited "acme-license.bbclass", whereupon ... well ...
acme-license.bbclass
====================
HOMEPAGE = "https://acme.com";
LICENSE = "Acme-Corp-License"
LIC_FILES_CHKSUM =
"file://${THISDIR}/../../files/acme-licenses/${LICENSE};
md5=deadbeef..."
*sigh* ... while this might save a couple lines per recipe file, i
can't believe this is a reasonable approach. has anyone else seen this
strategy?
in any event, i'm adding this to my current list of "stuff you might
want to avoid doing when using openembedded."
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149816):
https://lists.openembedded.org/g/openembedded-core/message/149816
Mute This Topic: https://lists.openembedded.org/mt/81547273/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
