Basically, the brew installer for rosdep needs to also accept a
dependency list, which is partly described here:

http://www.ros.org/reps/rep-0111.html#dependencies

In REP 112, the source manager specifies this external to the
rosdep.yaml file in order to keep metadata together.  In the case of
brew, I imagine it would be specified within the rosdep.yaml file.
This is not well-exercised yet, so we can work with you on making this
easy to do.

 - Ken

On Sat, Aug 13, 2011 at 2:00 PM, William Woodall <wjwwood@gmail.com> wrote:
> I am trying to get ROS going under OS X with homebrew, and I have run into
> an issue.  Several packages depend on python-numpy, which I would like to
> install through pip (homebrew doesn't provide a formula for this reason),
> but before I do that I need homebrew to install gfortran.  So, do I add a
> new rosdep to each package that also depends on numpy, or should there a
> mechanism for inter package management dependencies.  I know you can have
> several packages per installer rosdep (e.g. python: macports: python26
> python_select), but that is only enough if both dependencies are in the same
> package management system.
> For now I have just added another rosdep (gfortran) that uses homebrew to
> install and made that a dependency of roslib, but this is just a work
> around.
> Something to think about,
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> William Woodall
> Graduate Software Engineering
> Auburn University
> w@auburn.edu
> wjwwood@gmail.com
> williamjwoodall.com
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>