Changes between Version 5 and Version 6 of Ticket #67164, comment 17
- Timestamp:
- Apr 1, 2023, 10:43:48 AM (14 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #67164, comment 17
v5 v6 3 3 It was *specifically* only intended to deal with the fact that when macOS11 was released, in the early days of the SDKs they would change rapidly between minor versions. So 11.0 and 11.1 had different SDKs. MacPorts never expected this and it caused issues, so this regex was added. This happened because of how Apple changed the meaning of their OS versions. They went from 10.X being the major versions, with 10.X.n being the minor revision, to just X for the major and X.n for the minor. 4 4 5 We could think about just forcing the use of the completely version less SDk, but this is a change different to what we have done before. I would want to think through what side effects that could have. The current scheme is used as it ensures the build uses the SDK that matches their OS version. Switching to the versionless SDK could change this, e.g. on systems where Xcode provides multiple SDKs, and I am not sure we w nat that.5 We could think about just forcing the use of the completely version less SDk, but this is a change different to what we have done before. I would want to think through what side effects that could have. The current scheme is used as it ensures the build uses the SDK that matches their OS version. Switching to the versionless SDK could change this, e.g. on systems where Xcode provides multiple SDKs, and I am not sure we want that. 6 6 7 7 Also note, even this will *never* be a complete fix, it will still be possible for a user to have a different SDK path choice to whatever the binary installs are built with. As say the build bots built gcc using the Xcode SDK at a specific location, a user could still have only the CLT installed, or Xcode at a custom location. So the issue is still, at least in theory still there.