Jonathan Bohren

I think this is the "correct" behavior. As explained here: https://github.com/ros/catkin/issues/576 > You have to run `catkin_test_results`. In order for `run_tests` to run all tests even if some fail part...

> Seems like a good idea to me, but I probably don't understand all the implications. > > For a long time I have wanted to be able to define...

> So, maybe I'm missing something, but when do you ever set any environment variables manually? For myself, I always use the setup.*sh files. I also only ever use the...

> I threw together a spec for a similar tool a while back, but I haven't had time to implement it or try to incorporate it into the new catkin...

> Also, I want to point out that I designed this package so that tools like this can be developed externally. I would really like to avoid this package depending...

@wjwwood > I'm not sure about unsetting either, I would just open a new shell, it's really cheap, and that way you are sure that your env is clean. I...

@wjwwood > They aren't strictly required, and I think people would complain if we recommended taking the sourcing of setup files from their bashrc, but they work pretty well for...

> Catkin build has already been helpful for me. > > I work on so many diverse packages, that I find myself with eight or ten catkin_make workspaces, a big...

Now that the workspace extension discussion has been more focused in #48, I wanted to return to the potential implementation of a `catkin ws` verb. @wjwwood > I agree that...

Ok... so I've been having issues for about 15 minutes now where my overlay wasn't working. I am not sure how this happened, but I echoed `$CMAKE_PREFIX_PATH` and I saw...