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

[Ryan Schmidt]

On May 21, 2021, at 06:59, Christopher Nielsen wrote:

> 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?

Whoever updates protobuf3-cpp (or any other port that provides a library) is responsible for noticing whether the install_name has changed. If it has, that person is responsible for revbumping all ports that link with that library.