#53 modifies the thruster interface.
Because we are targeting upstream it complicates the rosdep and packaging. Rather than take my best guess and because my current awareness of the readiness of our packaging and rosdep dependency management is incomplete, I'm setting an issue to verify all this after we have merged.
From the comments:
Install docs / rosdep. Out of scope for this PR. I work from the drydock container setup, where most everything is apt installed,
and I have not had time to verify the packaging, rosdep and so on. I also find rosdep confusing to operate and maintain.
I do understand other workflows use it, but I don't think I'm the one to write that up, even if it is ready for primetime.
Beyond that, maintaining rosdep, the drydock apt installs and the packaging for each new feature is either
1) a lot of work if done manually, or
2) something the AI is not yet trustworthy enough to run open-loop.
I'll put up a separate issue to look at this outside the PR.
#53 modifies the thruster interface.
Because we are targeting upstream it complicates the rosdep and packaging. Rather than take my best guess and because my current awareness of the readiness of our packaging and rosdep dependency management is incomplete, I'm setting an issue to verify all this after we have merged.
From the comments: