Do all source packages need to be listed in .catkin file?

[jbohren]

One of the operational differences between using catkin_make and catkin build is that the .catkin files and ROS_PACKAGE_PATH generated by catkin build list each individual source package. Do they all need to be listed or could the source space just be listed?

Related to #221

• Keep the migration guide up to date if this changes

[jack-oquin]

I really like catkin_tools and use it a lot. But, having to re-source every time I add a package to a workspace is one of the few annoying usability problems I experience with it.

I would be grateful for almost any reasonable solution to that problem.

[NikolausDemmel]

+1

[jbohren]

I would be grateful for almost any reasonable solution to that problem.

So this is easy to do with the "linked-devel" configuration because we won't have to fight with the Catkin CMake code over editing the file. It's a bit messier with "merged-devel" mode, though, since Catkin will still be trying to write the package-specific source-space path to it. I think we're leaning towards the linked devel setup being the default, though.

[jack-oquin]

That sounds great, Jon. I was not aware of "linked-devel" configuration. Is that an option of the config verb?

[jbohren]

That sounds great, Jon. I was not aware of "linked-devel" configuration. Is that an option of the config verb?

It's part of what I developed as part of #196, which is now refactored into #276, pending review.

[jack-oquin]

That sounds like something I'd like to try. Thanks for the pointer.

[NikolausDemmel]

So this is easy to do with the "linked-devel" configuration because we won't have to fight with the Catkin CMake code over editing the file.

You mean this would be easy to realize with the linked devel space, but currently this is not the case with the linked devel space, right?

I don't know the answer to the original question though. We might need input from @wjwwood or @dirk-thomas .

[wjwwood]

I would guess that they are listed as narrowly as possible to avoid inconsistencies when you add a package to the source space but you haven't rebuilt the workspace yet, but I don't know for sure.