On 05/29/2012 12:23 PM, Tom Callaway wrote:
These are distro versions built from source. I'm trying to be a bit
sneaky/clever here. Let's take ros-fuerte-image-common as an example.
The spec file is named "ros-image-common.spec", and this is what the
beginning looks like:
%global codename fuerte
%global shortname image_common
Name: ros-%{codename}-image-common
Version: 1.8.0
Release: 1%{?dist}
Summary: Common ROS code for working with images
Thus, the Fedora git component name is "ros-image-common", and as
upstream bumps to "ginormous", we just change the value for codename and
rebuild. rpmlint notes that the .spec file name doesn't match the SRPM,
but this method is a lot simpler in the long run and it better matches
the experience that the upstream is providing on Ubuntu.
That's an interesting approach, it should help keep things more
consistent across distributions. Are the packages also doing a
Provides: without the codename, so rpm can handle upgrades properly?
We should check that, but I don't think so.
You're right, rospkg only provides /usr/bin/rosversion and a rospkg
python egg.
Okay. I'll upload them and post again when they're up.
Great! Looking forward to it.
I think we're going to need to do more than that. Is Tim (the PCL
maintainer) on this list? I still haven't found a working combination yet.
Tim is indeed on this list, I've CC'd him on this message in case he has
missed this thread.
~tom
==
Fedora Project
_______________________________________________
robotics mailing list
robotics@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/robotics
