Protobuf3-cpp update woes; strategy to avoid broken dependent ports?

[Christopher Nielsen]

We need to figure out a better way to deal with updates to ‘protobuf3-cpp’, as every time this port is updated, all dependent ports are broken. (Apart from a handful that folks manually rev-bump along with it.)

The problem is that every update results in the name of the dylib being incremented by one, breaking everything linked to it.

Does anyone know an easy fix?