Set Proprietary license for a recipe
From KoanSoftware Wiki
Revision as of 12:49, 11 July 2024 by Koan (talk | contribs) (Created page with "== Yocto Project - Set Proprietary license for a recipe == '''CLOSED''' is not '''commercial'''/'''proprietary'''! A common misconception is that setting '''LICENSE = "CLOSE...")
Yocto Project - Set Proprietary license for a recipe
CLOSED is not commercial/proprietary!
A common misconception is that setting LICENSE = "CLOSED" means the recipe in question is closed source, respectively proprietary.
This is not the actual case: the license value CLOSED has the meaning “do not care about the license of this recipe”.
This effectively disables all license tracking for this recipe and should be avoided.
The correct way to set a proprietary, nonstandard license is
LICENSE = "Proprietary"
This often correlates with being commercial, which is expressed by the flag
LICENSE_FLAGS = "commercial"
The commercial flag is automatically expanded with the recipe name, and can then be matched, therefore allowed for the build, as outlined in the first paragraph.
---
