Snapcraft ROS plugins should be using catkin_pkg instead of fetching all deps with rosdep
Metadata
Current evaluation
Closed without implementation. The proposal to replace rosdep with catkin_pkg for precise dependency parsing in Snapcraft ROS plugins was abandoned due to lack of activity.
Suggested action: —
No scores available.
Issue body
rosdep can't discriminate between build-time and run-time dependencies. As a result, ROS snaps include build dependencies when they don't need to, thus making them larger than necessary. Snapcraft should be using catkin_pkg to manually pull dependencies out of each package.xml.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The proposal to replace rosdep with catkin_pkg for precise dependency parsing in Snapcraft ROS plugins was abandoned due to lack of activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
5
|
close stale | Request to replace rosdep with catkin_pkg in Snapcraft's ROS plugin for finer dependency control and smaller snaps. Open for 6+ years with no maintainer feedback or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
65
Confidence:
90
Support Request:
10
|
close stale | Snapcraft ROS plugins use rosdep to fetch all dependencies, increasing snap size. Suggests switching to catkin_pkg to parse package.xml for build vs runtime deps. Untriaged, inactive for over 5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | Suggests replacing rosdep with catkin_pkg in Snapcraft ROS plugins to reduce snap size by separating build and runtime dependencies. Unaddressed for over six years with no maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
80
Support Request:
10
|
close stale | Use catkin_pkg instead of rosdep in Snapcraft ROS plugins to separate build and runtime dependencies, reducing package size. Currently unassigned, unlabelled, and inactive for over a year with zero comments. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.