On Wed, 2012-07-25 at 01:51 +0200, Jochen Sprickerhof wrote:
> * Bill Morris <bill@iheartengineering.com> [2012-07-24 19:29]:
> > So, I'm referring explicitly to the system /etc located in the root
> > directory. Most Ubuntu systems
> > have /etc/python, /etc/python2.6, /etc/python3.1 so I don't think it is
> > unreasonable to use /etc/ros, /etc/ros-fuerte, /etc/ros-groovy. Also I
> > like that if we have a symlink from /etc/ros to /etc/ros-fuerte it would
> > make it easy to switch the config to groovy by changing the symlink.
>
> If you want to set a system wide default, I would propose to use the
> update-alternatives system under /etc/alternatives/, which has a nice
> dpkg integration. In the long run it would be great if ROS would switch
> to shlib based dependencies (see dh_shlibdeps), proper API versioning
> and separation of development vs. runtime packages. This way we could
> lift the multiple version installation problem at some point.
>
> Cheers Jochen
Using update-alternatives to manage having two copies of ros installed
seems reasonable. However as far as I can tell it is designed for
managing binaries instead of config files.
Does any software besides the TurtleBot currently use the system
wide /etc/ros?
--
Bill Morris <
bill@iheartengineering.com>
I Heart Engineering
http://www.iheartengineering.com
<3
(text/plain)