Comment 13 for bug 1795214

Updating the vagrant box would be probably ~8-10 hours. The state of the art in creating vagrant base images for macOS is that you can do it with one command for macos 10.9-10.12, but 10.13 and 10.14 are done by building a 10.12 image, and then upgrading it.

Second, we have always built on the oldest system that we want to support. (We also haven't ever had issues like this in the past, where things break unless they're built on the newer OS.) Every time I look around at what other people are doing (Firefox, Chrome, brew...) they're all building on the oldest version they need to support. This may have changed, but when reading why, they said this is because of how dependencies get brought into the bundle. When you built it, do you know if every dependency that ends up in the bundle was also build with the min macOS version of 10.11? Knowing this was very hard before I did kicad-mac-builder. It should be easier to know that now, but it wasn't something I explicitly tested for.

If we want to try this, I support doing it, but we would need to do the regression test from the kicad-mac-builder README on 10.13 for sure, and it would be good to do 10.12 and 10.11. It's actually not super hard for me to do the test on 10.11, since I have the vagrant VM handy for it.

However, I do not really have more than an hour or two of time this week, so I could test a 10.14 built 5.0.1 on 10.11, but nothing really more. :( Do you think you, or another volunteer with macOS, has some time for this testing? I can outline what needs to be done and aim people at some directions tomorrow if so.

On another tangent, I saw a few other symbol editor issues this weekend here in Launchpad. Any chance those are related?