[MacPorts] #56135: protobuf-cpp in conflict with protobuf3-cpp
MacPorts
noreply at macports.org
Fri Jun 8 19:22:09 UTC 2018
#56135: protobuf-cpp in conflict with protobuf3-cpp
-------------------------------------------------+-------------------------
Reporter: btywoniuk | Owner: blair
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.4.2
Resolution: | Keywords:
Port: protobuf protobuf-cpp |
protobuf3-cpp protobuf-java protobuf3-java |
py-protobuf py-protobuf3 |
-------------------------------------------------+-------------------------
Comment (by ryandesign):
Replying to [comment:9 blair]:
> Some ports may not easily be upgradable. We commonly support multiple
versions of ABI incompatible libraries, e.g. serf0 and serf1, so why would
protobuf be different?
Well please decide what you want. If you want to offer multiple versions
such that different ports can use different versions of protobuf, they
need to not conflict; see #56102. That's what I originally suggested, and
that's what serf0 and serf1 do, but I don't think you responded to that
idea for protobuf, and others took charge and decided to upgrade
everything to the latest version instead. See https://github.com/macports
/macports-ports/pull/1628.
--
Ticket URL: <https://trac.macports.org/ticket/56135#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list