On Tue, Mar 23, 2021 at 3:13 AM Robert P. J. Day wrote:
>
> once again into the code base i'm poring over, and this time, it's
> about defining proprietary licenses for internal recipes.
The typical approach for recipes which build proprietary code is to
set LICENSE to "CLOSED" (and not define
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"
