Drop ROS Python package dependencies in debs #887
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.
When our Python packages are split into a separate
-modules
subpackage, it appears that the pattern is to retain the package distribution information in the main package, which contains the scripts.When our packages take dependencies on only the
-modules
subpackage, they need to omit the Python dependencies to preventpkg_resources
from looking for those missing packages. Instead, we rely on apt and dpkg to ensure that the dependencies are present.This shouldn't have any affect on non-debian installation of rosdep.
Fixes #886