All-
I've edited the "Creating a ROS package" tutorial to correct what I see as a
very common mistake that people make. Kevin is not the first person to ask
about this. The tutorial previously assumed the existence of a
~/ros_tutorials directory without ever telling the user to create one, then
issued vague instructions about fixing your ROS_PACKAGE_PATH if it didn't
work.
I hope the new flow makes it more clear for non-experts. Let's remember that
not all robotics folks are Linux experts, and I can relate to the
frustration of starting out on a new platform.
--Adam
Adam Leeper
Stanford University
aleeper@stanford.edu
719.358.3804
On Sun, Jan 23, 2011 at 3:27 PM, Jeremy Leibs <
leibs@willowgarage.com>wrote:
> On Sun, Jan 23, 2011 at 3:18 PM, maitri982 <kcramer@sapiosciences.com>
> wrote:
> >
> > Well...my first question found an issue with the instructions....so
> relative
> > newbies have there use i suppose.
> >
> > As for this question, I am in the ROS home directory which you get to via
> > issuing the roscd command...
>
> The roscd command takes you to the ROS_ROOT directory, which is not
> your home directory. If you've used a system-wide installation, such
> as from the debs, this will be in a restricted read-only part of your
> filesystem where you do not have write-permission, hence the failure.
>
> Your "home directory" (usually located at /home/username) in linux can
> typically be reached using "cd" or "cd ~". It is the directory on the
> computer where your user does have write permissions.
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
(text/plain)