Hi Robert,
On Wed, May 13, 2020 at 06:25:01AM -0400, Robert P. J. Day wrote:
>
> colleague added a new recipe to a build, got a warning "The license
> listed Unlicense was not in the licenses collected for recipe
> python-filelock" and, sure enough, that source was released under the
> "Unlicense" which i had never heard of:
>
> https://github.com/benediktschmitt/py-filelock/blob/master/LICENSE
>
> what is the standard strategy for dealing with that? should i just
> whitelist that license? has anyone else run into this "Unlicense"
> license?
>
You can add a license to your layer by doing the following in
conf/layer.conf:
LICENSE_PATH += "${LAYERDIR}/licenses"
and in there you put the Unlicense file named exactly the same with the
correct content. That's one way.
The other is to use NO_GENERIC_LICENSE[Unlicense] = "/path/to/Unlicense"
in the recipe.
If it's really widely used, maybe something to add to
openembedded-core/files/common-licenses/ ? So that you don't need any of
the suggested ways?
Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49391): https://lists.yoctoproject.org/g/yocto/message/49391
Mute This Topic: https://lists.yoctoproject.org/mt/74178255/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
