protobuf3-cpp: update to the current release (3.23.4)

[barracuda156]

I wanted to update grpc, but it turned out that our pretty outdated protobuf3-cpp does not have some required headers. Updating is desirable.

[mascguy (Christopher Nielsen)]

I have a new segregated port ready, providing the latest release. HOWEVER, I'm not sure that it's feasible to use it with non-leaf ports like grpc, as all dependents of the latter should also use it. (And that includes non-trivial ports like py-tensorflow.)

So please don't rush to update grpc with the new port, until more review, analysis, and discussion has occurred, relative to the implications.

[Christopher Nielsen <mascguy@…>]

In 7e50f3aada608a3f03515f9eae5eba01d4abb04b/macports-ports (master):

protobuf3-cpp-upstream: new segregated port, providing latest release
Closes: #67767

[mascguy (Christopher Nielsen)]

Duplicate of issue:67473

[barracuda156]

That was breezing fast, thank you!

*-upstream version builds fine on PowerPC.

[barracuda156]

Replying to mascguy:

I have a new segregated port ready, providing the latest release. HOWEVER, I'm not sure that it's feasible to use it with non-leaf ports like grpc, as all dependents of the latter should also use it. (And that includes non-trivial ports like py-tensorflow.)

So please don't rush to update grpc with the new port, until more review, analysis, and discussion has occurred, relative to the implications.

Yes, sure. (I know we do not make dependencies on -devel or -upstream ports for regular versions of other ports.)

[mascguy (Christopher Nielsen)]

Replying to barracuda156:

Yes, sure. (I know we do not make dependencies on -devel or -upstream ports for regular versions of other ports.)

This is one case where it's fine to use the new port. So that's not a problem.

Rather, it's the fact that other ports depend on grpc. And if any dependents also use protobuf, they would also need to use a matching version.

Make sense?