ROS (robot operating system) ports [team?]
rene at freebsd.org
Sat Mar 17 21:26:05 UTC 2012
Some (somewhat brain dump mode) thoughts about the ROS (devel/ros*)
ports  below:
- are there people who would be interested in forming a team? Together
with Chromium, Xfce, the Dutch translations, and "real life" this
becomes a bit too much for one person (I guess I underestimated the
effort :( ). Although the currently ported release (1.4) is still
supported upstream, release 1.6 has been there for some months
- since the ROS ecosystem and therefore the units in which these are
packaged seem get more finegrained at each release (1.0, 1.2, .. 1.8
which should be out soon), the question arises whether to keep just
the software originally planned (devel/ros-tutorials and devel/ros-nxt
 + dependencies) or also the software split off (which means more
ports, more testing, and more repocopies).
- because of the nature of the software, all ports need to be updated
to the next release in one commit to avoid breakage, although new
ports could be committed earlier as long as they are not connected to
- a generally positive development is that each release decreases the
amount of third party software built-in (this depends on the status of
several Linux distributions), but that also means that some newly
required third party might not be ported to FreeBSD yet and thus even
more ports to maintain.
- there is a lot more ROS software out there (enough for around 2000
ports), but some of it is only useful when run on the robots intended.
Obviously way too much for one person.
 http://www.ros.org/wiki/nxt (ROS bindings for the LEGO NXT robot)
More information about the freebsd-ports