Timeline for How to compile OSS binaries to replace the versions shipped with OS X?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2020 at 0:11 | comment | added | jksoegaard | Perhaps it's easier to copy over a newer version of xcodebuild? Or simply cross compile them, if you have access to a newer Mac (or perhaps run such a newer macOS version in a virtual machine). Going with the upstream BSD utilities will require you to more close compare the Apple version with the upstream version to see what you're missing out on. Some of it might be vital. | |
| Feb 27, 2020 at 0:06 | comment | added | Wowfunhappy | What makes the opensource.apple.com route difficult is they're all xcode projects without standard makefiles. And I can't open those new xcode projects in Mavericks's older xcode. I think I'm better off going with the upstream BSD utilities... | |
| Feb 27, 2020 at 0:05 | comment | added | jksoegaard | Sure, Apple is making lots of changes to these utilities. You'll find many commands that has options that only exist on macOS, or does stuff that is only possible on macOS (for example in using macOS specific OS services). An easy way to diff a full program like that is to download and unpack each version into their own folder. So you'll have a "bash_old" and "bash_new" folder for example. Then run this command in the terminal: "diff -r bash_old bash_new" | |
| Feb 26, 2020 at 23:40 | comment | added | Seamus |
That's a "good thing"! I wasn't aware that Apple was making any changes. Just out of curiosity, how did you do your diff? Since Apple doesn't use git, I've only tried d/l individual files & comparing them in BBEdit. Ummm... I'll happily submit this as a question if you want to get "paid" for this answer :)
|
|
| Feb 26, 2020 at 23:03 | comment | added | jksoegaard | Whether or not you consider the changes substantial is a matter of your opinion. When I diff the two versions of bash 3.2 (build 92 and 118) there's 1334 lines of difference. The change notes mentions at least two CVE's fixed (i.e. security vulnerabilities). | |
| Feb 26, 2020 at 23:02 | comment | added | jksoegaard | This was actually the point - i.e. to get the same major versions. If you upgraded bash to 5.0, you would expect all sorts of weird stuff and things not working anymore. It would not be drop-in compatible. By keeping bash at 3.2, you would get something which is highly likely to be drop-in compatible, but with security fixes. | |
| Feb 26, 2020 at 22:57 | comment | added | Seamus |
I like this approach, and it may be the most feasible. It certainly makes sense - at least to me. But wrt bash (as one example of a GPL-licensed package), the bash version today (MacOS 10.15) is still bash ver 3.2 - same as it was for MacOS 10.9 (and in fact since 2006). Are you aware that Apple has made any substantial changes to the sources for bash ver 3.2?
|
|
| Feb 26, 2020 at 22:10 | history | edited | jksoegaard | CC BY-SA 4.0 |
edited body
|
| Feb 26, 2020 at 22:07 | history | answered | jksoegaard | CC BY-SA 4.0 |