Split superpack into individual packages

[johnwason]

Currently, all of the Tesseract specific packages and closely related dependencies like Trajopt and Descartes are included in this single "superpack". It is built with colcon, and installed to $CONDA_PREFIX/opt/tesseract_robotics. Ideally, each individual package within the superpack should have its own conda package. Creating individual packages is significantly more challenging and time consuming, so the superpack strategy is currently being used.

Activation scripts are added to the package to call setup.sh or setup.bat in $CONDA_PREFIX/opt/tesseract_robotics so that colcon build output is correctly referenced by users.

[Tobias-Fischer]

Is this still the plan? We could help you in getting the individual packages up on conda-forge, if that is something you would be interested in. We can do it package by package, so that the transition is smooth. Now that it builds here okay, it should not be too hard.

[johnwason]

@Tobias-Fischer I think for the moment we are going to keep tesseract in its own channel since the development is still fairly rapid.

In terms of splitting into individual packages, this is pretty tricky because there are a large number of individual ROS packages that would need to be built separately and packaged into separate conda packages. The projects that were supporting my involvement with tesseract have ended, so I can't devote much time to reworking the packaging until more funding is available.