If you modified message_filters, you would have to rebuild just about
every stack anyways, so you're best off doing a source-based install
(e.g. rosinstall), and modifying it in place.

cheers,
Ken

On Mon, Aug 2, 2010 at 3:07 PM, Michael Styer <michael@styer.net> wrote:
> Aha. OK, that's clear enough! Thanks, Ken. I'll figure out another way
> to do it.
>
> Mike
>
> On Mon, 2010-08-02 at 14:58 -0700, Ken Conley wrote:
>> Hi Mike,
>>
>> You can't overlay a package that is part of the ROS core. Your options
>> are to rename your new package, or do a modified install.
>>
>> HTH,
>> Ken
>>
>> On Mon, Aug 2, 2010 at 2:53 PM, Michael Styer <michael@styer.net> wrote:
>> > Hello,
>> >
>> > If I wanted to install a modified version of a package in ROS core (e.g.
>> > message_filters) without removing the old version, how would I do it?
>> >
>> > I have ROS C-turtle installed via .deb packages in /opt/ros/cturtle/...,
>> > I have a local package directory in $HOME/ros/packages, and my local
>> > installation directory is listed first in my $ROS_PACKAGE_PATH. For
>> > non-core packages, this works OK. But rospack always looks in $ROS_ROOT
>> > first, regardless of what's in $ROS_PACKAGE_PATH (see line 1606 of
>> > rospack.cpp, SVN revision 10588), so it will ignore any overlay for
>> > packages in $ROS_ROOT. Is there another way to overlay core packages?
>> >
>> > Thanks!
>> >
>> > Mike
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users@code.ros.org
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>