Overview of the Apple source releases bump

[toonn]

Apple's source releases are only guaranteed to be compatible when they are part of a system release. Bumping all the packages together makes for a big diff that's hard to review.

To deal with this I'm bumping all the packages in a topological order. Since updating packages one by one isn't really an option I'm adding them in a separate attribute set. Once everything's merged we can switch over, hopefully requiring little more review effort.

I'll be opening PRs gradually and adding them to this list to preserve some overview.

• Introduce devtools 3.1.3 bsdmake #272998
• Introduce 10.13 CommonCrypto #272999
• Introduce 10.13 configdHeaders #273003
• Introduce 10.13 darwin-stubs #273006
• Introduce 10.13 hfs #273009
• Introduce 10.13 ICU #273010
• Introduce 10.9.2 launchd #273011
• Introduce 10.13 Libc #273012
• Introduce 10.13 libdispatch #273013
• Introduce 10.7 Libm #273014
• Introduce 10.13 libplatform #273015
  • Introduce 10.13 xnu #273016
    • Introduce 10.13 Libsystem #273017

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nix-macos-monthly/12330/47

[reckenrode]

Thinking ahead to after #229210 lands, is it possible the source selection stuff could be usable by other SDKs to pull in source-based components appropriate to their versions?

Apple's source releases are only guaranteed to be compatible when they are part of a system release.

Is that limited to the SDK or all source releases? I had most of adv_cmds-213 building with the 10.12 SDK (which I need to pick back up). How would that fit into this picture?

[toonn]

Re source selection, I haven't really thought about it. I think it would currently go in the wrong direction though, it enables subbing SDK things into a "source release" rather than the other way around, which I think is what we'd actually want, i.e., start from an SDK and only overlay bits of source releases when we manage to make them functional enough?

The compatibility is not an explicit policy, it's just a consequence of Apple's source dump model of FOSS.

[reckenrode]

Re source selection, I haven't really thought about it. I think it would currently go in the wrong direction though, it enables subbing SDK things into a "source release" rather than the other way around, which I think is what we'd actually want, i.e., start from an SDK and only overlay bits of source releases when we manage to make them functional enough?

I think we’re on the same page. Take an SDK then replace bits with source releases (or source-derived headers plus stubs) as we make them work.

The compatibility is not an explicit policy, it's just a consequence of Apple's source dump model of FOSS.

It was actually system_cmds I got updated not adv_cmds. Prompted by #295650, I’m planning to open a PR to update it once I confirm the stdenv bootstrap builds on both x86_64-darwin and aarch64-darwin.

[reckenrode]

#296321 is the system_cmds update PR.