← Back to issue list

Transition catkin plugin to use catkin build

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1693380
Type
issue
State
closed
Author
~annesteenbeek
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Requesting a transition from catkin_make_isolated to catkin build was closed without implementation. Zero comments and extended inactivity indicate the suggestion was abandoned.

Suggested action:

No scores available.

Issue body

The catkin plugin is currently using the catkin_make_isolated method to create the desired files needed for the snap. However, the current recommended method for constructing ros packages is using catkin build. Using catkin build would provide a more robust method for constructing the packages. More information about the differences between make and build can be found here: https://catkin-tools.readthedocs.io/en/latest/migration.html In the plugin source there are also some mentions of transitioning to catkin Tools.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Requesting a transition from catkin_make_isolated to catkin build was closed without implementation. Zero comments and extended inactivity indicate the suggestion was abandoned.
qwen/qwen3.6-35b-a3b The suggestion to transition the catkin plugin from catkin_make_isolated to catkin build was closed without implementation or discussion. The request remains unaddressed and effectively abandoned.
qwen3.6-35b-a3b-mtp-q6 Abandoned. The proposal to transition the catkin plugin from catkin_make_isolated to catkin build was closed without discussion or implementation.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1721168 Catkin plugin: support building the entire workspace snapcraft (launchpad) closed Request for Catkin plugin workspace-wide builds was closed without implementation or discussion. No pull requests were opened, indicating the feature request was abandoned.
72%