On Thu, Feb 2, 2012 at 12:09 PM, Jack O'Quin <
jack.oquin@gmail.com> wrote:
> On Thu, Feb 2, 2012 at 2:06 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:
>> On Thu, Feb 2, 2012 at 1:00 PM, Ken Conley <kwc@willowgarage.com> wrote:
>>
>>> I've resynced public now that we got a good rebuild last night. You
>>> probably want to avoid ros-shadow-fixed for the reasons Brian notes.
>>
>> ros-fuerte-common-rosdeps is there now, thanks
>>
>>> Please let me know if you see any other issues with Oneiric.
>>
>> Is there no longer a $ROS_ROOT/tools directory? I use them to find
>> things like rosemacs and rosbash in a distribution-agnostic fashion.
>>
>> I see rosbash has moved to share/rosbash. Still can't find rosemacs
>> (only its manifest.xml).
>
> Actually, the setup.bash generated by rosinstall still uses
> $ROS_ROOT/tools to find rosbash.
>
> Does rosco handle that correctly?
rosco does nothing more then checkout the tree. It's a very fast way
of adding a tree to an existing workspace (esp. if you have an alias
to add pwd to the ROS_PACKAGE_PATH), but its pro and con is just a
checkout tool.
- Ken
> --
> joq
(text/plain)