colcon fails to prioritize in-workspace RMF packages over installed versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 439
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
It was mentioned in #98 and has come up in other places as well. For some reason, colcon workspace overlays aren't correctly prioritizing in-source RMF package versions over the versions that have been installed on a machine. This usually works okay for ROS/ROS2 packages, so I have to assume there's something we can tweak in the cmake files of the RMF packages to help this work as intended.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the colcon overlay behavior described in the issue with the RMF workspace and an installed package version. Read the RMF packages' CMake files and compare their behavior with ROS/ROS2 packages. Done means in-workspace RMF packages are selected over installed versions during the overlay build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100