← Back to issue list

ROS plugins: allow skip keys for rosdep

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1882288
Type
issue
State
open
Author
~levi-armstrong
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to add skip keys option for rosdep in ROS plugins, allowing internal or custom dependencies not in public rosdep to be excluded. Open 6+ years with zero comments, no labels, and no maintainer engagement.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and zero comments across 2278 days (6+ years), showing no maintainer has ever assessed or categorised it. The repo still contains extensions/ros1 and extensions/ros2 directories, so the feature request may still be relevant, but it requires a maintainer to evaluate whether the rosdep resolution code (restructured in PR #1392) would accommodate a skip-keys option or whether the use case is better handled differently.

Impact: 35 Quick Win: 19.25 Staleness: 88 Complexity: 45 Confidence: 55 Support Request: 25

Issue body

It is common with developing ROS packages to have keys added to the package.xml that are not in the public rosdep. The following cases are below, but there may be more. 1. If these dependencies are internal dependencies and never get added to rosdep. 2. If a custom version of system library and we don't want to install locally. We would clone the repository into our workspace like VTK and add a package.xml with a unique package name, different than what is currently in rosdep and then use this in our packages.xml so catkin knows to build this package prior to our other packages. Propose adding the ability to list skip keys for rosdep to solve the issue.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19.25
Staleness: 88
Complexity: 45
Confidence: 55
Support Request: 25
needs triage Feature request to add skip keys option for rosdep in ROS plugins, allowing internal or custom dependencies not in public rosdep to be excluded. Open 6+ years with zero comments, no labels, and no maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 80
Support Request: 10
close stale Feature request to add a skip keys option to rosdep for internal or custom dependencies. Unassessed by maintainers with over 5 years of inactivity.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Feature request to add a configuration option for skipping specific rosdep keys in package.xml. Untriaged, no maintainer comments, inactive for over 5 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 10
needs triage Proposal to add a skip-keys feature for rosdep to handle internal dependencies and custom workspace packages. Untriaged, no maintainer response, and inactive for over 5 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 30
Confidence: 85
Support Request: 10
needs triage Feature request to add skip-keys configuration for rosdep, addressing internal or custom package dependencies. Currently untriaged, with no maintainer comments or labels in over five years.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#1392 (confidence 70%)

    Extracted rosdep from catkin plugin into snapcraft.plugins.internal.pullers to enable Ament/ROS2 support; any skip-keys feature would build on this restructured code.

  • Related To: snapcraft#1581 (confidence 60%)

    Merged PR adding pip-based dependency support to the Catkin plugin's rosdep resolver; modified the same rosdep resolution code path this feature would touch.

  • Related To: snapcraft#1810738 (confidence 55%)

    Open Launchpad bug requesting rosdep source list and stage packages customization for the Catkin plugin; similar theme of needing rosdep configuration flexibility for custom dependencies.

Related issues

No related issues found above the similarity threshold.