API review

Proposer: your name here

Present at review:

List reviewers

Question / concerns / comments

Enter your thoughts on the API and any questions / concerns you have here. Please sign your name. Anything you want to address in the API review should be marked down here before the start of the meeting.

- overlay:
    local-name: bt
    path: /opt/ros/bt
- svn:
    uri: https://
    local-name: common
    version: -r1600
- hg:
    uri: https://
    local-name: common_msgs
- git:
    uri: https://
    local-name: common_msgs
- bzr:
    uri: https://
    local-name: common_msgs
- installed:
    local-name: /opt/ros/boxturtle

New install instructions

Requires: /opt/ros/boxturtle/this.rosinstall

- installed:
    local-name: /opt/ros/boxturtle/ros
- installed:
    local-name: /opt/ros/boxturtle

5 layers

Any of which can come from source or debian, but all below any source one must be source:

boxturtle ros
boxturtle base
boxturtle pr2
boxturtle pr2all
boxturtle unreleased

Option 1: Recommended

Install from debian ros-boxturtle-pr2all

rosinstall ~/ros -p /opt/ros/boxturtle http://rosinstalls/wg_boxturtle_devel.rosinstall

Option 2:

Install from debian ros-boxturtle-pr2

rosinstall ~/ros -p /opt/ros/boxturtle http://rosinstalls/latest_pr2all_overlay.rosinstall http://rosinstalls/wg_boxturtle_devel.rosinstall

This can be used to develop stacks in the pr2all variant, by adding the development branch of whatever stack is requested on top.

Option 3:

Install from debian ros-boxturtle-base

rosinstall ~/ros -p /opt/ros/boxturtle http://rosinstalls/latest_pr2_overlay.rosinstall http://rosinstalls/latest_pr2all_overlay.rosinstall http://rosinstalls/wg_boxturtle_devel.rosinstall

This can be used to develop stacks in the pr2 variant, by adding the development branch of whatever stack is requested on top.

Option 4:

Install from debian ros-boxturtle-ros

rosinstall ~/ros -p /opt/ros/boxturtle http://rosinstalls/boxturtle_base_overlay.rosinstall http://rosinstalls/latest_pr2_overlay.rosinstall http://rosinstalls/latest_pr2all_overlay.rosinstall http://rosinstalls/wg_boxturtle_devel.rosinstall

This can be used to develop stacks in the base variant, by adding the development branch of whatever stack is requested on top.

Option 5:

Install all from source

rosinstall ~/ros http://rosinstalls/boxturtle_ros.rosinstall http://rosinstalls/boxturtle_base_overlay.rosinstall http://rosinstalls/latest_pr2_overlay.rosinstall http://rosinstalls/latest_pr2all_overlay.rosinstall http://rosinstalls/wg_boxturtle_devel.rosinstall

This can be used to develop stacks in the ros variant, by adding the development branch of whatever stack is requested on top.

Custom Code

After installing ROS and packages you likely will want to use your own code, the easiest way to add code is to create your own rosisntall file like the following:

- svn:
    local-path: my_stack_name
    uri: https://my.server/my/svn/url

Then you can simply add it to ~/ros by doing

rosinstall ~/ros my_rosinstall_file.rosinstall

This will add it to this.rosinstall in ~/ros.

Meeting agenda

This is a scoping back of rosinstall to basically just be a nice way to pull from source, and generate a setup file. It no longer depends on your environment.

How's the new API?
Change local-name to path? Can keep backwards compatibility
ROS_PACKAGE_PATH generation semantics.
- Should I list all packages
- Should I try to do proper semantic lookups
- Is it really a performance issue?
How should the Generate Versioned flag handle installed and overlays?

Usage: rosinstall PATH [URI] [options]

Options:
  -h, --help            show this help message and exit
  -u, --update          (deprecated unused)
  -p prepend overlay, --prepend=prepend overlay
                        prepend the install in this directory as an overlay
  -s SETUP_FILE, --setup_file=SETUP_FILE
                        create environment using an existing setup
                        file(deprecated)
  -o, --overlay         (deprecated unused)
  -n, --nobuild         skip the build step for the ROS stack
  --rosdep-yes          Pass through --rosdep-yes to rosmake
  --generate-versioned-rosinstall=GENERATE_VERSIONED
                        generate a versioned rosintall file

Conclusion

Package status change mark change manifest)

$/!\$ Action items that need to be taken.
Major issues that need to be resolved
$/!\$ list all paths for simplicity and clarity
change to externals (merge overlay and installed) test for this.rosinstall else fallback to installed
- seperate list at top
no more options $ri /opt/ros/bt http://fsadf.rosinstall
if directory look for this.rosinstall, else error
this.rosinstall mark installed, and refuse to reinstall
hide this.rosinstall to avoid tab completion .rosinstall
generate versioned rosinstall will generate a versioned local one and add comments for uncaptured externals

I had a follow up discussion with Josh and Ken about how to add a user workspace. To do this we brought up the idea of a workspace. But it's not different than an external except that it's not at the top of the list.

use "other" tag and interleave it detecting .rosinstall or not. (chain in if present)