[MacPorts] #66927: Boost: backport fix for context from boost181 or upgrade default one to boost181?
MacPorts
noreply at macports.org
Wed May 31 17:01:59 UTC 2023
#66927: Boost: backport fix for context from boost181 or upgrade default one to
boost181?
---------------------------+-------------------------------------------
Reporter: barracuda156 | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords: powerpc, leopard, snowleopard
Port: boost |
---------------------------+-------------------------------------------
Comment (by mascguy):
Replying to [comment:1 ryandesign]:
> So if we want to change the default boost version in the boost
portgroup, we have to simultaneously make one of two changes in every port
that uses the boost portgroup and does not specify the boost version:
either revbump and verify it still builds and works with the new boost
version, or modify the port to specify the old formerly-default boost
version.
>
> That would be a large amount of work to do at once, so I would be in
favor of an approach where, for every port that uses the boost portgroup
and does not specify the boost version, we modify them, gradually over
time (for example when updating them to a new version) so that they
specify the boost version. Then eventually we can remove the default boost
version from the boost portgroup, ensuring that every port that
subsequently uses the boost portgroup will have to specify the boost
version.
Yes, compared to all of that, applying the context fix - assuming the same
patch can be used verbatim (?) for 1.76 to 1.80 - is downright trivial.
So Sergey, if you want to submit a PR with that change for 1.76 to 1.80,
that's certainly fine. Particularly if it only affects PPC builds.
--
Ticket URL: <https://trac.macports.org/ticket/66927#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list