Agreed, I am just seeing what problems I run into with Homebrew, Macports may still end up being the best solution. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ William Woodall Graduate Software Engineering Auburn University w@auburn.edu wjwwood@gmail.com williamjwoodall.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Mon, Aug 8, 2011 at 10:09 AM, Brian Gerkey wrote: > On Mon, Aug 8, 2011 at 6:05 AM, William Woodall wrote: > > I see, so I would add the key value pair 'brew': HomebrewInstaller to the > > installers dictionary in the Osx class and rosdep will goto osx -> lion > -> > > and select the first key that exists in the installers dictionary? > > There will only be one installer for each (rosdep name, os name, os > version) tuple. > > > So, I would need to comment out all macports references in the > rosdep.yaml's > > in order for it to exclusively use brew? For experimenting I just > commented > > out the insertion of the MacportsInstaller into the installers dictionary > in > > the Osx class. > > That's what I was thinking, but following Tully's example below, you > could instead specialize each osx or macports rule to have both a > 'snow/macports' definition and a 'lion/brew' definition. That would > leave the current rules in place for Snow Leopard and head in the > direction of changing from macports to homebrew, starting with Lion. > I haven't tried homebrew, so I don't know whether to say that it's a > good way to go, but I'd be happy to try something other than macports. > > The broader thing to note here is that we should try to agree on which > package manager we'll use on a given version of OS X to bring in > UNIX-style libraries. I think that we'll be better off if we can > avoid mixing system dependencies from, for example, both macports and > homebrew. > > brian. > > > On Mon, Aug 8, 2011 at 1:08 AM, Tully Foote > wrote: > >> From REP 111 [1] With the new format I would suggest as follows, > >> assuming "graphviz" is a package brew knows how to install. > >> > >> osx: > >> lion: > >> brew: graphviz > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >