Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-02-18 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-02-10 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-02-07 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-01-29 | 1 | -119/+119 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-01-28 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-01-25 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-01-22 | 1 | -128/+128 |
| | |||||
* | Auto-update LICENSE file with current recipe licensestemp | github-actions[bot] | 2025-01-21 | 1 | -4/+4 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2025-01-15 | 1 | -4/+4 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2024-12-09 | 1 | -124/+124 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2024-12-06 | 1 | -1/+1 |
| | |||||
* | Auto-update LICENSE file with current recipe licenses | github-actions[bot] | 2024-12-05 | 1 | -10/+162 |
| | |||||
* | license: clarify the licensing for the project's metadata | Dima Zavin | 2019-01-10 | 1 | -0/+12 |
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> |