On Tue, Sep 20, 2011 at 9:10 PM, Jack O'Quin <
jack.oquin@gmail.com> wrote:
> I'd like to collect a list of all the driver packages we intend to
> convert to unary stacks.
>
> I believe all the camera_drivers stack could be repackaged. That would
> leave the camera_drivers stack, itself, empty except for dependencies
> on all the unary stacks for external compatibility.
>
+1. I like using the camera_drivers stack as a sort of "meta-package" to
pull in all of the officially support camera drivers. But at that point,
maybe it would be best to just supply a .rosinstall file and build a .deb
file that depends on all of the officially support drivers instead of
maintaining an actual stack in SVN.
>
> I am not completely clear as to how this should be structured in the
> ros-pkg SVN tree.
>
> Are there other drivers we should repackage in this way? Let's try to
> compile a (fairly) complete list.
>
Here's my list (I envision the current stack would continue on in some sort
of "meta-package" manner as discussed above):
Laser Drivers:
Hokuyo_node goes to a unary stack
Sick_driver stack that contains the sicktoolbox and sicktoolbox_wrapper
packages.
IMU Drivers:
We've only got the Microstrain driver, but I think keeping around an
imu_drivers meta-package would be consistent with the laser and camera
drivers.
Is there any intention of splitting the joystick_drivers into unary stacks?
- Eric
--
> joq
> _______________________________________________
> Ros-sig-drivers mailing list
> Ros-sig-drivers@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-sig-drivers
>
On Tue, Sep 20, 2011 at 9:10 PM, Jack O'Quin <
jack.oquin@gmail.com> wrote:
I'd like to collect a list of all the driver packages we intend to
convert to unary stacks.
I believe all the camera_drivers stack could be repackaged. That would
leave the camera_drivers stack, itself, empty except for dependencies
on all the unary stacks for external compatibility.+1. I like using the camera_drivers stack as a sort of "meta-package" to pull in all of the officially support camera drivers. But at that point, maybe it would be best to just supply a .rosinstall file and build a .deb file that depends on all of the officially support drivers instead of maintaining an actual stack in SVN.
I am not completely clear as to how this should be structured in the
ros-pkg SVN tree.
Are there other drivers we should repackage in this way? Let's try to
compile a (fairly) complete list.Here's my list (I envision the current stack would continue on in some sort of "meta-package" manner as discussed above):Laser Drivers:
Hokuyo_node goes to a unary stackSick_driver stack that contains the sicktoolbox and sicktoolbox_wrapper packages.
IMU Drivers:We've only got the Microstrain driver, but I think keeping around an imu_drivers meta-package would be consistent with the laser and camera drivers.
Is there any intention of splitting the joystick_drivers into unary stacks?- Eric
--
joq
_______________________________________________
Ros-sig-drivers mailing list
Ros-sig-drivers@code.ros.org
https://code.ros.org/mailman/listinfo/ros-sig-drivers
(text/plain)