rosinstall 0.5.30

Getting rosinstall<br /><br />Because it's used to install ROS software, rosinstall is a standalone program that you need to download. Get the latest version like so:<br /><br />wget --no-check-certificate http://ros.org/rosinstall -O ~/rosinstall<br />chmod 755 ~/rosinstall<br /><br />Usage<br /><br />usage: rosinstall [OPTIONS] INSTALL_PATH [URI]<br /><br />Options:<br />-u or --update (URI is optional only when using --update on an existing install)<br />-s SETUP_FILE or --setup=SETUP_FILE (use another setup.sh file to create env)<br />-o or --overlay (push current environment into setup.sh)<br />-n or --nobuild (don't perform a 'make core_tools' on the ros stack)<br /><br />Common invocations:<br /><br />initial checkout: rosinstall ~/ros http://www.ros.org/rosinstalls/boxturtle-base.rosinstall<br />subsequent update: rosinstall -u ~/ros<br /><br />After installation, rosinstall writes a bash setup file, called setup.sh, into INSTALL_PATH. Source this file to configure your environment variables.<br /><br />File format<br /><br />rosinstall works from a YAML file that tells it what repositories to check out from. The format is:<br /><br />- VERSION-CONTROL-TYPE:<br /> uri: URI<br /> local-name: WORKING-COPY-NAME<br /><br /> *<br /><br /> VERSION-CONTROL-TYPE : what kind of version control is used for this repository; supported types are:<br /> o<br /><br /> svn<br /> o<br /><br /> git<br /> o<br /><br /> bzr <br /> *<br /><br /> uri: the location of the repository<br /> *<br /><br /> local-name: the name to give the local directory into which the code is checked out <br /><br />NOTE: rosinstall will simplify the ROS_PACKAGE_PATH for checkouts that share a common local-name sub-directory. For example, if you put multiple checkouts in sub-directories of "stacks", it will set ROS_PACKAGE_PATH=stacks, instead of setting multiple paths per checkout.<br /><br />Example rosinstall configuration file<br /><br />This file checks out ros from the boxturtle tag, and uses the all svn:external in the wg-ros-pkg repository to get everything else.<br /><br />- svn:<br /> uri: https://code.ros.org/svn/ros/stacks/ros/tags/boxturtle<br /> local-name: ros<br />- svn:<br /> uri: https://code.ros.org/svn/wg-ros-pkg/all<br /> local-name: pkgs<br /><br />Please see the ROS Installation page for up-to-date instructions on using rosinstall with current configurations.<br /><br />Symbolic links<br /><br />In constructing the setup.sh file, rosinstall will fully dereference the INSTALL_PATH that you give it, following all symbolic links. So, for example, if your home directory is /home/user, which is a symbolic link to /storage1/user, and you do this:<br /><br />rosinstall /home/user/ros http://www.ros.org/rosinstalls/boxturtle-base.rosinstall<br /><br />then the setup.sh file will contain lines like these:<br /><br />export ROS_ROOT=/storage1/user/ros/ros<br />export ROS_PACKAGE_PATH=/storage1/user/ros/stacks/common:...<br /><br />i.e., the path to your installation was expanded. This doesn't usually present a problem, but it can be an issue if you expect the location of your installation to move. In that case, you should edit the setup.sh file to point to the symbolic link.

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Boxturtle,  Checkouts,  Current,  Directory,  Environment,  Install Path,  Installation,  Localname,  Location,  Multiple,  Repository,  Rosinstall,  Setupsh,  Symbolic,  Update,  Version,  Versioncontroltype
Users rating:	0/10