We currently provide multiple versions of the Gazebo recipes and use the version information in the vendor packages to set the preferred version.
This is time consuming and error prone. It would be better to automatically generate this information based on official dependency information.
Some of this information is available here: https://github.com/gazebo-tooling/gazebodistro
One possible way to accomplish this would be to write a Python script that read the collection file for a Gazebo release. Then it should determine the appropriate git tags and version information. This information should be saved in a cache file with a date and time stamp to record the commits at the time of recipe generation. This helps provide traceability and reproducibility.
We currently provide multiple versions of the Gazebo recipes and use the version information in the vendor packages to set the preferred version.
This is time consuming and error prone. It would be better to automatically generate this information based on official dependency information.
Some of this information is available here: https://github.com/gazebo-tooling/gazebodistro
One possible way to accomplish this would be to write a Python script that read the collection file for a Gazebo release. Then it should determine the appropriate git tags and version information. This information should be saved in a cache file with a date and time stamp to record the commits at the time of recipe generation. This helps provide traceability and reproducibility.