Options for packages????

Maybe all of the rosdep.yaml files should have

osx:
  leopard:
    macports: py26-pip
    homebrew: pip
    source: …
  lion:
    macports: py27-pip
    homebrew: pip
    source: …

Not sure if that is possible and it is starting to look a little crazy, but manageable. Can you rank order the entries with the first one (macports) being the preferred, the second homebrew being experimental (unless William pulls of a crazy amazing move to get everything running on homebrew like his Auburn team's on-side kick to win the game) and then have source as a last resort if all else fails. I think everyone will have either macports (80%) and the rest homebrew (15%) leaving the few source compiler people to do what they want … of course I totally made up those numbers :)

Thoughts?

I still think we need to bump the official python for OSX up to 2.7 so it is more in line with the homebrew guys. You don't want too many variable when chasing down error.

On Sep 2, 2011, at 2:44 PM, Brian Gerkey wrote:

> On Fri, Sep 2, 2011 at 10:37 AM, Kevin Walchko <kevin.walchko@gmail.com> wrote:
>> I don't like installing source code I can't easily remove. That is why I put up with macports.
> 
> hi Kevin,
> 
> That's a fair point.  But it's also an indictment of entire source
> rosdep approach to pulling in third-party stuff.  Can you suggest an
> alternative?
> 
> We need a way to install code that isn't available (or at least isn't
> available at the needed version, or in the needed configuration) from
> an OS's package manager.
> 
> 	brian.
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users