Generate LICENSE files on ros2 pkg create. #650
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
That is, if the '--license' command-line argument is one of
the ones that ament_copyright knows, fetch the license text
out of ament_copyright and place it in 'LICENSE' at the
root of the package.
Signed-off-by: Chris Lalancette clalancette@openrobotics.org
Here's the current list of strings that will trigger the creation of the LICENSE file:
One thing to be aware of here is that this is the first use of
ament_copyright
in anexec_depend
. I don't think that should be a problem, but it is something to think about.An enhancement we could do here is to add the SPDX identifiers to the license tuple in ament_copyright, and then use that instead. I don't mind strongly which way we go, but we should think about it and be deliberate; changing it later on will be difficult. Feedback is most welcome.
@nuclearsandwich @tfoote @gbalke @ros2/team FYI.