[MacPorts] #56252: macosx_version should contain the full macOS version
MacPorts
noreply at macports.org
Sun Apr 8 14:14:47 UTC 2018
#56252: macosx_version should contain the full macOS version
-------------------------+--------------------
Reporter: ryandesign | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.4.99
Keywords: | Port:
-------------------------+--------------------
I'd like to see the full macOS version (e.g. `10.12.6`) [ticket:52575 in
the main.log], but annoyingly, `macosx_version` only contains the major
macOS version (e.g. `10.12`).
[changeset:94e87f11199ca14c8b8a554d84e675eaa9db917c/macports-base Jeremy
briefly changed it to the full version], but there are places in MacPorts
base that assume it is only the major version, so that change was quickly
reverted.
Can we revisit this idea of changing (some might say correcting) the
meaning of `macosx_version`? Most of the ports that use the variable
already accommodate this, since they use `vercmp` when testing that
variable. I [changeset:35e1788ba94778e0e024b566c9858100a2e214c3/macports-
ports fixed the wine ports] which were doing the comparison wrong, and I
[https://github.com/macports/macports-ports/pull/1553 sent a PR for
libcxx]; after that's merged, all the ports should be ok.
Base still has a few places that use string comparison on that variable,
but I'm happy to fix those up if we agree to make this change.
Alternately, we could keep `macosx_version` as is and add a new variable
for the full version, as [https://lists.macports.org/pipermail/macports-
dev/2013-October/024675.html Josh suggested], but I don't think that's the
best solution.
--
Ticket URL: <https://trac.macports.org/ticket/56252>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list