Dane Springmeyer

@allieoop and I took a closer look at this issue. The workaround, in short, when going from dev release to tagged release is to: - switch from keyword of `tarball`...

This work is still outstanding and would be a useful project. I don't have time to work on it but I did get the mason bash scripts running on alpine...

A potential Dockerfile could look like: ``` FROM alpine:3.8 AS build ENV CXX=clang++ CC=clang RUN apk add --no-cache bash ca-certificates curl libstdc++ clang build-base ```

Thank you for reporting this. /cc @kkaefer who wrote those `sed` lines and will have the best idea of how to test/land this fix.

That is great @jfirebaugh. What needs to happen at the mason level to support this? My understanding is: - `mason.ini` store the raw include paths like `include_dirs={prefix}/include` (e.g. for geometry.hpp...

Looks like a typo, thanks for noticing!

Per chat with @tmpsantos - we are actually going to keep this functionality and @tmpsantos will be adding a unit test to ensure it stays working.

removing the fallback to a compile if the install fails would be fine.

We should definitely not do anything to make debug packages harder. That raises the issue of whether debug packages should be a customized script or if mason should make it...

Note: I've been finding and fixing many packages build with autotools that are not being built with any optimization flags. After incrementally fixing a dozen or so (to help enable...