William Woodall

@cpaxton thanks for reporting the issue. I think the line `os.chmod(env_file_path, stat.S_IXUSR | stat.S_IWUSR | stat.S_IRUSR)` is the culprit, but I'm not sure how it should be changed. Can you...

Hmm I didn't know that. In my opinion I think the entire build out for the stage (make or cmake) should be printed when there is an error. It's often...

> The problem is that some people just symlink colorgcc to gcc. I don't think we should be trying to call it exactly. Instead, we should probably just grep stdout...

We could potentially set the value of `TERM` when using `catkin_tools` to something that will prevent `colorgcc` from colorizing (and therefore combining stderr and stdout): https://github.com/colorgcc/colorgcc/blob/master/colorgccrc.txt#L39 From https://github.com/colorgcc/colorgcc/blob/master/README: > colorgcc...

Also, I think starting in gcc 4.9 colorized output is built into gcc, so this might be only a temporary issue: https://gcc.gnu.org/gcc-4.9/changes.html (look for `-fdiagnostics-color=always`)

> I think that will probably break all colors, since other tools also rely on this variable. You're probably right... Though at least some tools only care about whether or...

Not right now. You can neither put it in the workspace configuration nor a global configuration (there is no global configuration, but we've talked about having one for a while)....

@mikepurvis that all sounds right to me. Spinning off a daemon each time to update the file sounds scary, but I've done it the past with bloom (to check the...

@ianjfrosst if you don't consider exec depends, then you cannot know that you can run (or test) a package after building it.

> @wjwwood the issue is that exec_depend is causing package builds to be serialized. If you catkin build a workspace, you could build a package and its exec depends at...