Link legacy macOS build on website

[ann0see]

We now provide two builds for macOS: legacy and the normal one. We should link both on the macOS page.

[gilgongo]

What's the reason? I've not been following the macOS stuff.

[ann0see]

The new build with Qt 5.15.2 supports macOS Big Sur without UI glitches and multiple small bugs but breaks compatibility to old versions of macOS. See: jamulussoftware/jamulus#1687 and especially jamulussoftware/jamulus#1768

[gilgongo]

Oh OK, so it's just a straight OS version split on the download page. I assume we therefore maintain two versions of 3.8.0+ from now on?

Just trying to work out what impact this has on what we say on the website.

[ann0see]

I assume we therefore maintain two versions of 3.8.0+ from now on?

Yes. I think we could just link the legacy build from the macOS page the same as for the SourceForge mirror

[gilgongo]

How does that work with the links exactly then? Do we have two {{ site.download_file_names.mac }} variables and change the SF link to point to the versions directory instead or something?

[ann0see]

I think something like this would be enough:

[gilgongo]

So will we need to update these links for each release (until we abandon support for anything lower than macOS 11)?

[ann0see]

Unfortunately yes.

But it's all in _config.yml

[ann0see]

Ok. Just pushed this change to translate

[ann0see]

@ignotus666 @jujudusud I also added the legacy link to your translations. You can translate them later on

[jujudusud]

Done for FR, to be merged.