On 2022-06-02 17:41:09, enh via Toybox wrote: > Oh, yeah, I think *especially* for macOS where pretty much everyone is > always on the latest version anyway, unless your Mac equivalent of the > seven year rule is "support the oldest macOS release that still gets > security backports", there's no reason to do this. It's pretty rare they > add anything significant anyway.
Um do you mean there's no one running old unsupported versions of macOS? My ancient Mac Mini is running an old unsupported macOS. I don't think they have a supported version for it. One of these days I'll try to upgrade it, but I know the latetst version wont install, though there might still be a supproted version. I rarely use it these days, and got more important things keeping me busy. > On Thu, Jun 2, 2022, 17:34 Rob Landley <[email protected]> wrote: > > On 6/2/22 12:43, enh via Toybox wrote: > > 10.15 is currently the oldest macOS release that's still getting > > security updates (probably until the end of 2022, if history is any > > guide). Without this, toybox built on newer versions will by default > > target that version. > > > > Tested by adding -v and seeing that the "sdk" in use changed from > > 12.0.0 by default to 11.0.0 with this flag (Apple has multiple > > version numbering schemes; my kernel says it's 21.5.0 already!). > > Hmmm... Switching which version github is building is one thing, but > switching > the default in scripts/portability.sh seems a bit micromanagey? (I > wouldn't > think an -mtune for Linux would belong there...) > > Rob -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
