[ros-users] Deb source packages

Tully Foote tfoote at willowgarage.com
Mon Jun 18 07:48:14 UTC 2012

Hi Rich,

Due to a long history of interweaved lineage PCL and ROS datatypes collide.
 We have not forked PCL as much as applied a patch to make it use our
generated messages instead of the stripped down versions built into PCL.
 This previously was done inside PCL upstream, however it has proven easier
to patch new releases than maintain the functionality within PCL.  Also it
does not require PCL to have anything ROS specific inside it's release.
 The git-buildpackages repositories allow us to reimport upstream and
reapply our patches on top of new releases as they come out.  If there is a
patch release to the version we have used we can take it up, and plan to.
 We cannot take up major API breaking releases.

There has also been an initiative to release renamespaced versions of pcl
1.6 as pcl16 as a backport into Electric.  I'm not sure of the current
status of that effort.


On Fri, Jun 15, 2012 at 7:01 PM, Rich Mattes <richmattes at gmail.com> wrote:

>  On 06/12/2012 01:49 PM, Tully Foote wrote:
> Hi Tim,
>  That is where we build the debs from.  In one of our next rounds of
> upgrades we hope to provide the sources via apt-get source on
> packages.ros.org.  But I suggest pulling from the git-buildpackage repos
> as that will be easiest, and you can keep your own fork of the repo if you
> want for your architecture specific sources.
>  Tully
>  PS: For reference all the new style debians in fuerte they are listed at
> : https://github.com/ros/rosdistro/blob/master/releases/fuerte.yaml
> Hi Tully,
> Are there any plans to integrate the changes to PCL upstream instead of
> maintaining a wg fork?  From my analysis, the only changes are that the wg
> fork includes the generated message headers, .msg files, and some ROS stack
> metadata.  I opened a bug upstream[1] and was going to take a crack this
> weekend at having PCL's buildsystem handle generating the message headers
> and installing the stack files when USE_ROS is enabled, but if someone else
> is working on it I'd rather not duplicate the effort.
> Thanks,
> Rich
> [1] http://dev.pointclouds.org/issues/699
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users

Tully Foote
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20120618/693c60bc/attachment-0004.html>

More information about the ros-users mailing list