Commit Graph

7 Commits

Author SHA1 Message Date
github-actions[bot]
f0b2c665ef Auto-update LICENSE file with current recipe licenses 2025-04-28 15:52:29 +00:00
github-actions[bot]
5ea5f3a7be Auto-update LICENSE file with current recipe licenses 2025-04-25 11:37:00 +00:00
github-actions[bot]
aa1a3c026b Auto-update LICENSE file with current recipe licenses
Some checks failed
Update LICENSE file / update-license (push) Has been cancelled
2025-04-15 15:49:05 +00:00
github-actions[bot]
12ef152d2c Auto-update LICENSE file with current recipe licenses
Some checks are pending
Update LICENSE file / update-license (push) Waiting to run
2025-04-02 15:47:50 +00:00
github-actions[bot]
9f3fd09b93 Auto-update LICENSE file with current recipe licenses 2025-04-02 09:18:47 -03:00
github-actions[bot]
705708b135 Auto-update LICENSE file with current recipe licenses
Some checks are pending
Update LICENSE file / update-license (push) Waiting to run
2025-04-02 11:27:07 +00:00
Dima Zavin
73926e3059 license: clarify the licensing for the project's metadata
Presently, the recipe files in meta-freescale are under an ambiguous
license. There is a EULA file at the root, but it's clearly not meant
to apply as the default license as it is only explicitly called out in
a few recipes and mirrors the language of the LSDK. The yocto upstream
projects are meant to be distributed under a more liberal license than
the LSDK.

There are several licenses listed is custom-licenses/, but those again
only apply to specific recipes (e.g. NXP-Binary-EULA).

The license for the recipes themselves (and for the layer metadata, etc.)
is not clear and is problematic when attempting to host a mirror of this
code. So, add a LICENSE file that describes this situation, and provide
a reference copy of the MIT license (taken from poky/meta/).

Signed-off-by: Dima Zavin <dmitriyz@waymo.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2019-01-10 10:59:06 -02:00