← Back to issue list

catkin plugin: recursively merge rosinstall files

View original Github issue

Metadata

Project
snapcraft
Number
#1714
Type
issue
State
closed
Author
sergiusens
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action:

No scores available.

Issue body

Estimate: 4 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. This will require us to have a concept of being finished. How do we know that we’ve finished pulling everything necessary if we’re doing so in a recursive manner?

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b 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.
qwen/qwen3.6-35b-a3b The catkin plugin feature to recursively merge rosinstall files was closed and abandoned without implementation. Recursive fetching logic was never added due to unresolved design questions and lack of discussion.
qwen/qwen3.6-35b-a3b The request to recursively merge rosinstall files in the catkin plugin was closed without implementation. With zero comments and no linked resolution, the feature was abandoned after over a year of inactivity.
qwen/qwen3.6-35b-a3b A request to add recursive rosinstall file merging to the catkin plugin was closed without implementation. With zero comments and over eight years of inactivity, the feature was abandoned.
qwen3.6-35b-a3b-mtp-q6 The request to recursively merge rosinstall files in the catkin plugin was closed without implementation. Zero comments and no associated pull requests indicate the feature was abandoned.
qwen3.6-35b-a3b-mtp-q6 The catkin plugin feature request for recursively merging rosinstall files was abandoned due to prolonged inactivity. No implementation or alternative solution was provided, leaving the capability unaddressed.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
83%
#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.
79%
#1715 catkin plugin: detect and gracefully handle rosinstall clashes snapcraft closed 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.
79%
#1314 catkin plugin: add support for rosinstall files snapcraft merged Merged. Introduces a rosinstall-files property to the Catkin plugin, allowing Snapcraft to manage ROS workspace dependencies. Approved by a reviewer and merged after resolving CI test delays. Resolves Launchpad bug 1533735.
74%
#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.
74%
#28 Add support for building ros/catkin based projects snapcraft closed Feature request for ROS/catkin build support was closed without resolution. No implementation or merge occurred, indicating the request was abandoned or deferred indefinitely.
71%