Skip to content

WIP: Use only CATKIN_IGNORE to ignore packages, not COLCON_IGNORE/AMENT_IGNORE#688

Merged
timonegk merged 1 commit intocatkin:mainfrom
janstrohbeck:ignore_only_catkin_ignore
Apr 3, 2025
Merged

WIP: Use only CATKIN_IGNORE to ignore packages, not COLCON_IGNORE/AMENT_IGNORE#688
timonegk merged 1 commit intocatkin:mainfrom
janstrohbeck:ignore_only_catkin_ignore

Conversation

@janstrohbeck
Copy link
Copy Markdown
Contributor

@janstrohbeck janstrohbeck commented Aug 19, 2021

My use case: I have a shared source space in which both ROS1 and ROS2 packages reside (the migration to ROS2 is ongoing). Now I want to build the ROS1 packages using catkin_tools, same as before, and the ROS2 packages using colcon. To do this, I place CATKIN_IGNORE files in the ROS2 packages, and COLCON_IGNORE files in the ROS1 packages.

Problem: catkin_tools/catkin_pkg ignores the ROS1 packages due to an existing COLCON_IGNORE.

I think catkin_tools should ignore ROS1 packages only when there is a CATKIN_IGNORE file present, and not when COLCON_IGNORE/AMENT_IGNORE is present.

This PR depends on a PR in catkin_pkg: ros-infrastructure/catkin_pkg#307

@timonegk
Copy link
Copy Markdown
Member

By the way, because I just noticed that I never responded to this PR: I like your suggestion, but we have to wait for the merge of the other pull request, of course.

@rhaschke
Copy link
Copy Markdown
Contributor

rhaschke commented Apr 3, 2025

we have to wait for the merge of the other pull request, of course.

@timonegk: ros-infrastructure/catkin_pkg#307 was merged meanwhile.

@timonegk
Copy link
Copy Markdown
Member

timonegk commented Apr 3, 2025

@rhaschke thanks for the update, I will merge it in the evening and create a new release.

@timonegk timonegk force-pushed the ignore_only_catkin_ignore branch from 0ae3953 to 3e11efb Compare April 3, 2025 19:04
@timonegk timonegk force-pushed the ignore_only_catkin_ignore branch from 3e11efb to aa87b7e Compare April 3, 2025 19:08
@timonegk timonegk merged commit 7257b5c into catkin:main Apr 3, 2025
0 of 15 checks passed
@timonegk
Copy link
Copy Markdown
Member

timonegk commented Apr 3, 2025

@wjwwood I just tagged 0.9.5 and pushed it to PyPI. I don't know if you still do the apt releases, but if you do, could you please pull the trigger there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants