Creating an issue to track any ROS guix channel that may appear in the wild.
The main issue I see with it, is the maintenance burden. So it's likely for a group to check that all ROS packages built with guix behave as expected, lockdown a specific guix channel commit hash that packages have been tested with, etc...
https://github.com/pyros-dev/pyros-channel
Something I started quickly. still WIP. I intend to use it to hold pyros-related packages, to make things deployable with a guix workflow.
Current plan is to holding the ROS packages I depend on as well, but I aim to depend on another channel entirely...
Creating an issue to track any ROS guix channel that may appear in the wild.
The main issue I see with it, is the maintenance burden. So it's likely for a group to check that all ROS packages built with guix behave as expected, lockdown a specific guix channel commit hash that packages have been tested with, etc...