On Sun, Jan 23, 2011 at 6:38 PM, Tully Foote wrote: > On Sun, Jan 23, 2011 at 11:56 AM, Jeremy Leibs > wrote: >> On Sun, Jan 23, 2011 at 11:53 AM, Jack O'Quin >> wrote: >> > So, the reason my installs still have the old name is because they >> > were originally installed before this change? Updating them does not >> > seem to have any effect. >> I don't know if rosinstall re-generates those files on an update.  It >> probably should.  Also, you need to have updated the rosinstall >> command itself.  I believe the command is "easy_install -U rosinstall" > After you have updated rosinstall as stated above 0.5.12 or higher will have > the new scripts.  If you run  `rosinstall path_to_rosinstall_directory` to > updated it will regenerate the new setup files. I just tried updating it on a Lucid system. My python-setuptools package is already at the latest version (0.6.10-4ubuntu1). I ran "easy_install rosinstall", but the rosinstall.egg in /usr/local/lib/python2.6/dist-packages/ is only at level 0.5.8. Since I don't really understand easy_install very well, it's hard to be certain I did the required steps correctly. But, I did the obvious things. Updating with that rosinstall leaves the old setup.sh scripts in place. They still source rosbash. That works for me, as long as I don't update my .bashrc to invoke setup.bash yet. But, it feels like we've got "one foot on the dock and one foot in the boat". --  joq