You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Announcement [PR](https://github.com/conda-forge/conda-forge.github.io/pull/1993); TODO [list](https://github.com/conda-forge/conda-forge.github.io/issues/1844#issuecomment-1675953297), context & discussion. Ecosystem is forcing us to move on (libcxx-trick doesn't help anymore); ≪1% users affected
- Do we want to formulate a more specific support policy? (10.13 is EOL for 3 years already; CPython might jump to 10.15/11.0)
51
+
- (CHL) Could consider following Apple's lifecycle, but be aware that may force us to drop `osx-64` before we're ready to. (Expect ~3 yrs left on Apple's support for such hardware)
52
+
- (JK) If we do a NEP-29 style annoucement, we should align with other projects to make sure `conda`/`conda-forge` is not the odd ecosystem out.
53
+
- MB: macOS 10.14 (Mojave) is the last version to support 32-bit (https://support.apple.com/en-us/HT208436)
54
+
- MB: We could point people with old Macs to https://github.com/dortania/OpenCore-Legacy-Patcher or the like
55
+
- Action items:
56
+
- Someone check the announcement PR to make sure we have all the technical details correct
57
+
- Add `__osx>=10.13` as `run_exports` to the appropriate compilers packages <- actually a clobber file
-[ ] (HV) [bikeshedding at the end]`-dev` vs. `-devel`
93
+
- came up in boost unification, current PR uses the latter based on Isuru's [rationale](https://github.com/conda-forge/boost-feedstock/pull/164#issuecomment-1681583116)
94
+
- matches Anaconda naming & CDTs, does not match recent CUDA feedstocks, tangentially related to distro discussion (RHEL vs. Debian). We should try to choose one.
0 commit comments