Dane Springmeyer

Update here: - We are now targeting clang++ 3.9.1 for all newly built packages - There have been no reported problems with mixing binaries across clang++ versions (which we are...

Update again: * We are now targeting clang++ 5.0.0 for all newly built packages: https://github.com/mapbox/mason/pull/512 * There have still been no obvious problems with mixing binaries across recent clang++ versions...

No reason that I'm aware of. Can you point to an example package that does this?

:+1: mason should be able to be installed anywhere, and we should probably stick with unix conventions in the future: `bin/mason` for the command and `share/mason/` perhaps for scripts? Then...

Considering dodging this via #536 (moving to circle) based on the assumption that network is faster/more reliable on circle (don't have proof for this, just hope).

As some background for anyone who has not dealt with conflicting system libraries and custom libraries before I'll add a bit more background... Say that your app depends on `zlib-system`...

Working on trying to understand the failure at https://github.com/mapbox/mapbox-gl-native/issues/802 by starting to add tests to `zlib-system` package: https://github.com/mapbox/mason/commit/ecdd669267bf04822704b944eb4cf25fcc2d0644

Statically linking zlib is fine if you can be sure that all code statically links the same zlib (allowing the linker to discard duplicate symbols). Situations where this would not...

In adding tests for zlib-system (#66) I've noticed that `MASON_SDK_PATH` gets clobbered for `ios` such that the SDK for the iPhoneSimulator gets used instead of the iPhone: https://github.com/mapbox/mason/blob/master/mason.sh#L58-L67. This makes...

sounds good @kkaefer