ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Hi v01d,
So I'm the guy currently managing those Python scripts for Arch. I took a look at bloom a while ago, when Fedora support was being added. Most of the PKGBUILDs could be generated that way, it's been on my todo list for a long time. There were a few quirks, but then again I was not familiar with bloom at all, and Arch packages are quite different from their Debian counterpart.
Among the things that we could try to improve in the PKGBUILDs are the Python-related sed
replaces that we need to do since Arch moved to Python 3 as its default Python years ago, and ROS is not entirely ready for Python 3 yet (or maybe for the next release?). As for the rest, things improved quite a lot w.r.t. multi-distribution support, but human interventions when APIs break are still required once in a while (e.g. the Gazebo 7 upgrade I made, but the related ROS packages did not release their changes yet).
Providing user-made binary packages is possible on Arch, but what's missing is a repository where I could push such packages. Also, ROS packages are not the only issue: their dependencies should be binary-released as well, and there's a bit of work there (*cough* PCL *cough*).
Since ROS answers may not be the best place for long discussions, feel free to join the Gitter chat associated with the project: https://github.com/bchretien/arch-ros-stacks