Mike Purvis
Mike Purvis
@jbohren Curious for your thoughts on this.
Could also just be separate files, depending what the specific needs are. There's already `.built_by` and `.catkin_tools.yaml` in the root of the build space, so maybe a `.packages.yaml` file, with...
What do you mean about unique to each build? Just that the file would wiped and rewritten? A potential alternative would be to treat this as a log, put it...
Gotcha. Sounds good. @tspicer01 or I will take a look at getting a PR up for this.
I'm interested in this too, although my use case with bundle builds is a workspace of multiple hundreds of packages, where there are a handful of one-off flag modifications, but...
I can't promise immediate attention, but with some design guidance I might be able to move this along. Do we have a sense what the timeline is for 0.4 and...
I'm going on parental leave in January and may have some time to look at this, but I'm discouraged from putting in a lot of effort given the lack of...
Thanks, and yay! I :heart: catkin_tools.
@ahoarau Most of the guts of the needed "merge" functionality is present in the [`merge_envs` function](https://github.com/catkin/catkin_tools/blob/8b2d68f65f6a43d732dd1a2467f287b8fecfd3ae/catkin_tools/jobs/utils.py#L66-L103) which I contributed in #449. Currently, this functionality is used only internally to make...
The fundamental issue is that CMake packages typically generate installspaces which contain absolute paths and aren't relocatable (unlike catkin packages), and later packages in the same build need to find...