Dependency graph up to the ros-core meta-package. Each node represents a package, and each edge represents a dependency upon another package. ros-core depends on over 175 packages, whereby around 100 packages are pulled in from Conda-forge (such as Boost and Numpy) and the remaining packages are dependencies on other ROS packages such as rosbag and rostopic.

Contexts in source publication

Context 1

... has a builtin mechanism to turn a directory of "package recipes" into an Azure Build Pipeline definition. Figure 2 shows the dependency graph up to the 'ros-core' metapackage. The packages are topographically sorted and the pipeline is then split into multiple stages, where each stage needs to wait for the previous one to finish. ...

Context 2

... has a builtin mechanism to turn a directory of "package recipes" into an Azure Build Pipeline definition. Figure 2 shows the dependency graph up to the 'ros-core' metapackage. The packages are topographically sorted and the pipeline is then split into multiple stages, where each stage needs to wait for the previous one to finish. ...