On Wed, Feb 23, 2011 at 3:23 AM, Miguel Prada Sarasola
<
miguel.prada.sarasola@gmail.com> wrote:
> I just found another issue with how this setup file works.
>
> I upgraded from cturtle to diamondback, and as I source the setup.sh in the ni stack _after_ sourcing the setup.sh in diamondback, the setup file in the ni stack overwrites the package path, removing the diamondback directory and including the cturtle one. I now this can be easily fixed (by rerunning rosinstall if I'm not mistaken, or even manually fixing the setup file), but it wouldn't be necessary if the setup file did append the ni stack dir to $ROS_PACKAGE_PATH instead of a hardcoded value that's created by rosinstall.
If you are still seeing setup.sh and not setup.bash, you are probably
using an out-of-date rosinstall script. To update it, run this:
$ sudo easy_install -U rosinstall
There are many ways of setting $ROS_PACKAGE_PATH. Which you use does
not matter as long as it's done correctly. You probably do not want to
source two different setup.bash scripts.
One of the nice things about rosinstall is its ability to create a
composite setup.bash containing all the stacks it manages.
http://www.ros.org/wiki/rosinstall#Common_Use_Cases
--
joq
(text/plain)