[Toybox] [PATCH] macOS: target 10.15.

[David Seikel]

On 2022-06-03 09:43:31, enh via Toybox wrote:
>    On Fri, Jun 3, 2022 at 9:27 AM Rob Landley <rob at landley.net> wrote:
> 
>      On 6/2/22 19:41, enh 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. 
> 
>      If you think the mac AOSP prebuilts should require the latest macos
>      version to
>      run, that's your call. I don't really have a MacOS policy because I'm
>      not
>      familiar enough with MacOS: they actively exclude any developer who
>      doesn't pay
>      to play. (And sadly Darwin died in 2006, although I'll blog about that
>      rather
>      than blathering here.)
> 
>    sorry, i seem to have confused everyone here...
>    note that [unless we check in the "our official min is
>    $lowest_version_supported_by_apple" patch] anyone who builds toybox will
>    get a version that targets their builder's os version. so AOSP is actually
>    getting whatever it's running on, and someone with a 10.4 machine from
>    2005 would get 10.4. that was always true and hasn't changed.
>    what we've done [so far] is say "our CI is now testing the latest release
>    that github supports at any given time" [which, modulo a month or so, is
>    Apple's current release]. so our "even if we're not paying much attention,
>    github will tell us if we've screwed up" bar is set at "current". which i
>    think was all we were ever trying to do with github CI anyway --- "is it
>    broke?". (google's security policies also mean i can't really test on
>    anything older than "current" [modulo a month or so, like github].)
>    the change is that we used to _also_ ask github CI to test "oldest
>    still-supported macOS release". i still don't think we've ever heard from
>    a user who needs that, and i don't remember ever breaking one but not the
>    other [all the breakages i can remember have been solid "linux-isms" that
>    wouldn't work on any macOS release], so i don't think anything's changed
>    in practice.

Just to re-iterate, for development purposes I'm NOT a current Mac user,
but I plan to be one again some time in the future, so I can port my
toybox based thing to macOS.  When I start doing that is when I'll worry
about what version of macOS I run on my Mac, and hope I wont have to buy
a new Mac.  Though the new M1 based Mac Minis look nice, and maybe a M2
or later Mac Mini might be around when I get around to it.  I'm on a
pension these days though, Apple hardware tends to be a bit expensive.

Sure I recently built a super desktop computer, but that was due to our
government at the time (may they rest in pieces) throwing my money
around.  Long story short, they let us access our superannuation for
COVID.  If you don't know how that works in Australia, I'm not about to
explain it.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.