Create test workspace with 2 packages with different dependencies. Run rosdep collection script with defaults file that specifies --packages-select one_package. Check output script for its dependencies.
Continue above experiment into build phase and check that build directory only contains the one package
Description
It should be possible now to customize the
colcon buildwith arbitrary arguments such as--packages-up-toby providing a colcon defaults file.If the user can easily provide this, then we can avoid having to expose any explicit arguments.
Side effect, this should enable customization of
colcon listfor the rosdep collection step.Related Issues
N/A
Completion Criteria
colcon build(build step) andcolcon list(in rosdep gathering step)Implementation Notes / Suggestions
Suggest a
defaults.yamlfile at root of workspace, andbuild_workspace.shsets theCOLCON_DEFAULTS_FILEorCOLCON_HOMEenvironment variable appropriately. See https://colcon.readthedocs.io/en/released/user/configuration.html#defaults-yamlTesting Notes / Suggestions
Create test workspace with 2 packages with different dependencies. Run rosdep collection script with defaults file that specifies
--packages-select one_package. Check output script for its dependencies.Continue above experiment into build phase and check that
builddirectory only contains the one package