catkin plugin: detect and gracefully handle rosinstall clashes
Metadata
Current evaluation
Rejected. Maintainer cancelled the feature because vendors do not require recursive rosinstall parsing or clash detection, and recursive fetching is already supported. Low demand and implementation complexity led to abandonment.
Suggested action: —
No scores available.
Issue body
Estimate: 5 days
The Catkin plugin currently supports parsing rosinstall files to pull the various repositories that make up the workspace that it will build. A request from Shadow Robotics is to add the ability to then look inside the pulled workspace for more rosinstall files, and fetch their repositories as well. This is not supported by rosinstall alone. Would be nice if Snapcraft was smart enough to know if rosinstall files clash with each other (e.g. file A requires repo foo, hash 1234, file B requires repo foo hash abcd).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Rejected. Maintainer cancelled the feature because vendors do not require recursive rosinstall parsing or clash detection, and recursive fetching is already supported. Low demand and implementation complexity led to abandonment. | |
| qwen/qwen3.6-35b-a3b | — | — | Rejected due to low vendor demand and high implementation cost. Maintainer noted recursive rosinstall fetching is already supported, making clash detection unnecessary. Issue closed as abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to detect rosinstall file clashes in the catkin plugin was rejected. A maintainer determined the feature would add unnecessary complexity with little practical benefit, as vendors do not require it, and recommended cancelling the extension. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected due to low vendor demand and high implementation cost. Recursive rosinstall parsing and clash detection for the catkin plugin will not be implemented unless explicitly requested. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected due to low vendor demand and high implementation effort. Recursive rosinstall fetching is already supported, making clash detection unnecessary. The feature was abandoned unless explicitly requested later. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1714 catkin plugin: recursively merge rosinstall files | snapcraft | closed | The request to recursively merge rosinstall files in the catkin plugin was closed without implementation or discussion. The feature was not added and the issue appears abandoned. | |
| #1533735 Catkin plugin: Support rosinstall files | snapcraft (launchpad) | closed | Closed without implementation. The request to add rosinstall file support to the Catkin plugin was abandoned due to zero comments and prolonged inactivity. | |
| #1934 catkin plugin: support recursive rosinstall files | snapcraft | merged | Merged. Introduces a recursive-rosinstall boolean option to the Catkin plugin, enabling automatic resolution of nested rosinstall files unsupported by wstool. Defaults to false. Resolves #1714 following successful review and CI checks. | |
| #1473 catkin plugin: rosinstall-files is a pull property | snapcraft | merged | Merged a maintainer correction updating the catkin plugin. The rosinstall-files property was incorrectly configured as a push property and has been changed to a pull property. Approved by two reviewers with a three-line fix across two files. | |
| #1548404 Catkin plugin: Can't handle rosdep resolving to multiple packages | snapcraft (launchpad) | closed | Closed without resolution. The Catkin plugin fails when rosdep returns multiple packages on a single line, treating it as one invalid name. The issue was abandoned due to zero comments and no proposed fix. |