Hi all,
It's been a little while since our last discussion about ROS packaging. I
know I got bogged down with real life and dropped the ball with respect to
the f18 feature process work, but there has been some progress on that
front. I've got the four ROS Utilities on the ROS_Packaging[1] wiki page
done, and I'm currently working through the 12 ROS Core packages. I've
been stashing them on my fedorapeople page [2]. I think we can get at
least the core packages for ROS Fuerte done for f18 and then update them
all to Groovy once it comes out.
There are a few issues I wanted to discuss:
1) ROS package naming and other packaging guidelines:
Right now we're using the name ros-%{rosdistro}-packagename based on Tom's
initial packaging efforts. Would it make sense to have a ros macro file
that defines things like %{rosdistro} vs declaring it in each package?
Additionally, since a lot of the ROS packages that come from github have
very similar structure, perhaps we can create a ROS package template, and
lay out guidelines for which virtual Provides to add to each package and
document where we deviate from the core ROS stacks (for example, i've moved
/usr/etc/langs to /etc/ros-langs for the message generation subsystem)
2) Packaging Fuerte vs. waiting for Groovy:
Groovy is supposed to have significant changes to filesystem layout to make
it more FHS friendly. Based on my work with Fuerte, it's not too hard to
beat Fuerte's core packages into FHS compliance, so maybe we can focus on
getting the core stacks done for Fuerte and then once Groovy is out we
upgrade the core in f18+ and start reviewing additional well-known stacks
for groovy.
3) EPEL
Should we spend a lot of time targeting el6 (and even el5) as we are
packaging? A lot of research institutions seem to be running redhat,
though I don't know how many IT departments rely on EPEL vs. the RH
supported repos. My inclination is that if it's not too difficult, we
should try to at least support el6; el5 might be a bit harder due to the
lack of CMake 2.8 in the repositories.
In the meantime, I will submit rosinstall, rosdep, and rospkg for review
sometime this week since they're straightforward python packages which are
required by the upstream source installation directions (I've already got
vcstools reviewed and in Fedora).
Rich
[1] https://fedoraproject.org/wiki/SIGs/Robotics/ROS_Packaging
[2] http://rmattes.fedorapeople.org/rospackages/
Hi folks,
I was trying to build ROS on fedora. Not an rpm or anything, just plain
ROS as described here[1]. Quite at the end, I ran into the issue with
pcl[2], which will be resolved in pcl-2.0. I was wondering if anyone
knew a workaround for the time being to get ROS working on fedora, until
we package it up?
The page[1] is a little incomplete. This is the list of packages I
needed to install:
python-empy python-nose log4cxx-devel wxGTK-devel qt4-devel
wxPython-devel yaml-cpp-devel opencv-devel tinyxml-devel
There's also a tiny change in the rosdep that needs to be made[3]
Until we get ROS packaged up, I was thinking of putting up a wiki page
(or updating the ROS page) detailing how one can use ROS on their fedora
system. (It installs stuff in /opt etc., but I don't think that can be
helped at the moment. I'm using a vm at the moment)
If any one has any pointers on the pcl issue, please do let me know. If
possible, I could host a separate repo on my fedorapeople space with a
ros-specific pcl version.
[1] http://www.ros.org/wiki/fuerte/Installation/Fedora
[2] http://dev.pointclouds.org/issues/699
[3] https://code.ros.org/trac/ros/ticket/3929
--
Thanks,
Warm regards,
Ankur: "FranciscoD"
Please only print if necessary.
Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIGhttp://fedoraproject.org/wiki/User:Ankursinhahttp://dodoincfedora.wordpress.com/
Hi folks,
I'm Ankur. I've been around the Fedora community for a few years now.
I'm a package maintainer and an ambassador, and well, a general
community monkey. I've just begun a masters by research course which is
based around mobile robot navigation in a dynamic environment. I've been
working with IMUs, the NAO and a few other things currently.
I intend to continue with robotics after masters (a PhD) and think I
could therefore help with the robotics SIG. I've seen that ROS is being
packaged for Fedora[1]. Since I'm already a package maintainer, I can
help with packaging and reviewing. Are there any packages that require
attention at the moment, a road plan maybe?
I haven't any experience with ROS (yet).
[1] https://fedoraproject.org/wiki/Features/ROS_Fuerte
[2] https://fedoraproject.org/wiki/SIGs/Robotics/ROS_Packaging
--
Thanks,
Warm regards,
Ankur: "FranciscoD"
Please only print if necessary.
Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIGhttp://fedoraproject.org/wiki/User:Ankursinhahttp://dodoincfedora.wordpress.com/
