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

Add colcon-override-check as a recommended dependency #15

Merged
merged 1 commit into from
Apr 11, 2022

Conversation

cottsay
Copy link
Member

@cottsay cottsay commented Mar 15, 2022

The intent of this change is that a typical installation of colcon from debs would result in installation of the colcon-override-check extension, but that specifically excluding or uninstalling that package won't result in colcon-common-extensions' dependencies being unmet.

The intent of this change is that a typical installation of colcon from
debs would result in installation of the colcon-override-check
extension, but that specifically excluding or uninstalling that package
won't result in colcon-common-extensions' dependencies being unmet.
@cottsay cottsay self-assigned this Mar 15, 2022
Copy link
Contributor

@nuclearsandwich nuclearsandwich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm down to try this out!

Comment on lines +52 to +54
[options.extras_require]
recommended =
colcon-override-check
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's good either way but is extras_require[recommended] an accepted community norm or is this something that we're trailblazing based on distro packaging conventions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've found no precedent. Fundamentally, the purpose of extras_require is to list optional or recommended dependencies that aren't strictly required, so we're not very far out by using it like this. That said, I found no uses of the name recommended, and this is also essentially a Python metapackage, for which there is little precedent to begin with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants