On 05/29/2012 12:16 PM, Rich Mattes wrote:
Great! Are you just making copies of their ubuntu packages at the
moment? Are you shooting to replace packages like "fuerte-bullet" with
distro versions of packages at some point? Using fuerte in all the
package names will also force a mass re-review each time another release
is done, unless these are just targeted for a fedorapeople repo.
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.
The official install instructions[1] still use them, and they still
may
be helpful for package generation and for developing or downloading and
building third-party stacks that aren't packaged in Fedora. I think
that the rospkg package might overlap with your ros-fuerte-rospack for
instance.
We should check that, but I don't think so.
It would be great if you tossed them up on fedorapeople as you go,
I'd
be interested in helping you test and debug them in my spare time.
Okay. I'll upload them and post again when they're up.
Haven't tried PCL trunk yet, but I will do so shortly.
If it works, we can probably update our package to an SVN snapshot.
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.
~tom
==
Fedora Project