Hi like @Martin_Guenther and @awesomebytes have said we do use our on custom distribution on top of ROS.
We started doing this before the new buildfarm was created and the documentation linked by @nuclearsandwich was created, so what we've done may differ with the steps detailed there.
We freeze make a snapshot of a ROS distribution's repositories (let's say Kinetic), and then we release our custom ROS packages or our own software. Our package naming scheme is pal-erbium-my-pkg-name.
We install them on /opt/pal/ and ROS keeps installed in /opt/ros. Instead of sourcing /opt/ros/kinetic/setup.bash, you source /opt/pal/erbium/setup.bash, and this file already sources kinetic and makes the overlays behave as expected.
[quote="Paul_Bovbel, post:2, topic:5205"]
* theres no way to get two base workspaces in `/opt/ros` to overlay via catkin
[/quote]
As long as you source the original ROS workspace (say Kinetic) before building your custom distro, I believe the overlays work flawlessly.
We usually have 3 levels /opt/ros/kinetic, /opt/pal/erbium and working workspace.
---
[Visit Topic](
https://discourse.ros.org/t/ros-ourdistro-style-add-on-rosdistro/5205/6) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)