Track packages that are released in ROS build farm but are/should be in conda-forge about robostack.github.io HOT 9 OPEN

apriltag (https://github.com/AprilRobotics/apriltag, https://repology.org/project/apriltag/versions) is another package that is released as part of ROS but could also be a standalone package in conda-forge, see discussion in stack-of-tasks/pinocchio#1700 .

from robostack.github.io.

I added eigenpy to the table @wolfv .

from robostack.github.io.

There's also fcl_catkin which is used by exotica, and should pull in conda-forge's fcl instead of building it.

/cc @wxmerkt

from robostack.github.io.

Regarding fcl_catkin, once upstream makes a new FCL release (flexible-collision-library/fcl#532) and updates it as ros-noetic-fcl, I am considering unreleasing fcl_catkin from Noetic altogether (ipab-slmc/exotica#735 makes its use redundant). The primary motivation for it was to provide bleeding edge FCL when there was no ros-*-fcl and now that there is, it has outlived its purpose.

from robostack.github.io.

In ROS2, we now also have tvm-vendor which should be unvendored.

from robostack.github.io.

Related ROS Discourse discussion: https://discourse.ros.org/t/release-package-requiring-custom-version-of-system-dependency/18200 .

from robostack.github.io.

An interesting case of this packages are the one that do not depend on anything ROS-specific and so can go in conda-forge, but that use the ROS-like strategy of a single repo with multiple directories that contain different interdependent CMake or Python packages (see for example https://github.com/ethz-adrl/ifopt or tesseract, https://github.com/ros-industrial-consortium/tesseract tesseract-robotics/tesseract#419).

An example of this kind that is already in conda-forge is orocos-kdl (see https://github.com/conda-forge/orocos-kdl-feedstock/blob/master/recipe/meta.yaml) that indeed is using a multi-output recipe structure for which each "package" results in a different output. I don't know if vinca can help in this case, even if the recipe then goes in a usual conda-forge feedstock.

from robostack.github.io.

A strange package of this kind is urdf_parser_py/urdfdom-py. A rather old version is availably on PyPI: https://pypi.org/project/urdf-parser-py/ , however new versions are regularly released in ROS: under the urdfdom_py name: https://index.ros.org/r/urdfdom_py/ . The fact that is not on conda-forge is blocking the release of downstream packages that depend on it: ami-iit/adam#26 .

from robostack.github.io.

xref: BehaviorTree/BehaviorTree.CPP#644

from robostack.github.io.