Wait... what part of this env variable is portable?
<env name="PYTHONPATH"
value="/home/advait/svn/robot1/src/libraries:/home/advait/svn/robot1/src/libraries/katana:/home/advait/ros/ros/core/roslib/src:/usr/lib/python2.5/site-packages"
/>
If your user name changes on the remote machine, wouldn't your launch
file stop working? It seems that the remote machine's $PYTHONPATH
would be more likely to know where all its libraries are than a
.launch file, right?
-hai
On Thu, May 20, 2010 at 11:28 AM, Advait Jain <
advait@cc.gatech.edu> wrote:
> I think the goal is to ensure that launch files continue to
> work whether you launch nodes locally or remotely by
> putting the environment variables in the launch files
> and not relying on how the bashrc is set up.
>
>
> On Thu, May 20, 2010 at 11:02 AM, Armin Hornung
> <HornungA@informatik.uni-freiburg.de> wrote:
>>>
>>> You can change environment variables through your launch file:
>>> http://www.ros.org/wiki/roslaunch/XML/env
>>>
>> True, but shouldn't it be the default within a launch environment to
>> keep the system-wide environment variables intact, so that a node
>> behaves identically from the command line and in the launch file?
>>
>> Otherwise, you would have to adjust the launch file in question on each
>> machine to point to exactly the same PYTHONPATH as is already configured
>> on the machine...
>>
>>
>> Cheers,
>> Armin
>>
>> --
>> Armin Hornung Albert-Ludwigs-Universität
>> www.informatik.uni-freiburg.de/~hornunga Dept. of Computer Science
>> HornungA@informatik.uni-freiburg.de Humanoid Robots Lab
>> Tel.: +49 (0)761-203-8010 Georges-Köhler-Allee 79
>> Fax : +49 (0)761-203-8007 D-79110 Freiburg, Germany
>>
>> _______________________________________________
>> 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
>
--
Hai Nguyen
CS, Robotics
(text/plain)