<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/12/2012 01:49 PM, Tully Foote
wrote:<br>
</div>
<blockquote
cite="mid:CAJTOrSTyqc_JeYP7Nh9+s6Fo-_T+47fyxJHM2M_rUUJ4FGRccw@mail.gmail.com"
type="cite">Hi Tim,
<div><br>
</div>
<div>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 <a moz-do-not-send="true"
href="http://packages.ros.org">packages.ros.org</a>. 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. </div>
<div><br>
</div>
<div>Tully</div>
<div><br>
</div>
<div>PS: For reference all the new style debians in fuerte they
are listed at : <a moz-do-not-send="true"
href="https://github.com/ros/rosdistro/blob/master/releases/fuerte.yaml">https://github.com/ros/rosdistro/blob/master/releases/fuerte.yaml</a><br>
</div>
</blockquote>
<br>
Hi Tully,<br>
<br>
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.<br>
<br>
Thanks, <br>
<br>
Rich<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://dev.pointclouds.org/issues/699">http://dev.pointclouds.org/issues/699</a><br>
</body>
</html>