Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{common}: add license map to fix BSD license issue #1256

Closed
wants to merge 1 commit into from

Conversation

jiaxshi
Copy link
Contributor

@jiaxshi jiaxshi commented Nov 13, 2024

Since BSD file was removed in YOCTO/scarthgap, some ROS recipes build failed due to cannot find BSD license.

Map BSD to BSD-3-Clause similar to YOCTO/kirkstone.

Fix issue #1208

@robwoolley Could you please review and check if this change is fine to merge?

Since BSD file was removed in YOCTO/scarthgap, some ROS recipes
build failed due to cannot find BSD license.

Map BSD to BSD-3-Clause similar to YOCTO/kirkstone.

Signed-off-by: Jiaxing Shi <[email protected]>
@jiaxshi
Copy link
Contributor Author

jiaxshi commented Nov 13, 2024

I know the right way is to ask the maintainer of each projects to add explicitly license context. Before that, how can we use meta-ros?
I raised issue on several ROS projects, only got one clear response.

@shr-project
Copy link
Contributor

FWIW: I believe this is wrong and I've replied before with links to superflore where it was discussed how to fix this properly.

But I no longer maintain or use meta-ros, so I don't really mind, just my 2c.

@robwoolley
Copy link
Collaborator

I don't feel comfortable using the SPDXLICENSEMAP for BSD, just because I have caught examples in ROS named "BSD" that were not BSD-3-Clause.

Thanks for trying to help though. It is an annoying problem.

@robwoolley robwoolley closed this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants