-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Kconfig: Add ALLOW_CUSTOM_PERMISSIVE_COMPONENTS license option #18017
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
Kconfig: Add ALLOW_CUSTOM_PERMISSIVE_COMPONENTS license option #18017
Conversation
016e207 to
1fe587f
Compare
|
@ThePassionate the term "PROPRIETARY_COMPONENTS" is too broad, and in fact the license used on whetstone benchmark it not proprietary, but a permissive "non-standard" (like BSD, MIT, APACHE, etc) This is what chatgpt reported about this license: So, although it is not a standard open-source license, it is not proprietary. |
Thanks, i have updated to CUSTOM_COMPONENTS. |
|
Suggestion: move it to ALLOW_CUSTOM_PERMISSIVE_COMPONENTS to make the name more clear to understand |
Add a new license configuration option for components that have custom permissive licenses which are not covered by the standard license options (BSD, MIT, GPL, etc.). This option allows projects to explicitly opt-in to using components with custom permissive licenses that allow free use, modification, and distribution but may have specific attribution or notice requirements. Also update the License Setup documentation section to include this new option. Signed-off-by: makejian <[email protected]>
1fe587f to
10bde48
Compare
You are right! using "ALLOW_CUSTOM_PERMISSIVE_COMPONENTS" is more accurate and clearer. We want to cover permissive licenses that allow free use but have non-standard terms. @acassis |
Kconfig: Add ALLOW_CUSTOM_PERMISSIVE_COMPONENTS license option
Summary
This PR adds a new license configuration option
ALLOW_CUSTOM_PERMISSIVE_COMPONENTSfor components that have custom permissive licenses which are not covered by the standard license options. This addresses the need identified in nuttx-apps#3343 for handling components like the Whetstone benchmark which have custom permissive license terms.Changes
Files Modified
Kconfig
ALLOW_CUSTOM_PERMISSIVE_COMPONENTSconfig option under "License Setup" menuDocumentation/quickstart/configuring.rst
ALLOW_*_COMPONENTSoptions with descriptionsTechnical Details
New License Option:
Integration:
ALLOW_ICS_COMPONENTSin the License Setup menun(disabled) for safetydepends on ALLOW_CUSTOM_PERMISSIVE_COMPONENTSImpact
Usage
Enable option with:
CONFIG_ALLOW_CUSTOM_PERMISSIVE_COMPONENTS=y
Testing
Configuration option verified.
Reference
which discussed in apache/nuttx-apps#3343