Warn users when installing ARM64 Runtime and Targeting Pack installers on x64 MacOS.

[AraHaan]

From https://github.com/dotnet/arcade/issues/8107#issuecomment-993233804

Currently I face this issue when I use arcade on one of my own self made projects where it produces it's own runtime pack and targeting packs (to learn how all the bits worked) and this results in this issue on MacOS where users using x64 macbooks can accidentally install the ARM64 builds resulting in runtime issues at startup when they try to use it. As such I think some sort of warning on the installation bundles of some sort should be done, or have it say "Sorry, this computer is not ARM64, try the x64 version instead.". The result would make users know they was about to do a bad thing from the beginning and not wonder "Why does my program crash at startup?".

[ericstj]

@AraHaan can you link to what installers you're trying to install?

I just gave this a try using our public installers and they both block installation: https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-6.0.1-macos-arm64-installer

Dec 14 15:42:54 Erics-MBP Installer[9934]: Installation checks failed.
Dec 14 15:42:54 Erics-MBP Installer[9934]: Installation check failure.  . Microsoft .NET Runtime - 6.0.1 (arm64) can’t be installed on this computer..

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-6.0.101-macos-arm64-installer

Dec 14 15:46:46 Erics-MBP Installer[9964]: Installation checks failed.
Dec 14 15:46:46 Erics-MBP Installer[9964]: Installation check failure.  . Microsoft .NET SDK 6.0.101 (arm64) can’t be installed on this computer..

[ericstj]

This is implemented here: https://github.com/dotnet/installer/blob/8b9782a074c51ef9f8b8b0608870c23ed77df7f5/src/redist/targets/packaging/osx/clisdk/Distribution-Template#L5

And here, for runtime: https://github.com/dotnet/runtime/blob/eb4834060d7c6d3bbdb2eae8a3312c8a6a726146/src/installer/pkg/sfx/bundle/shared-framework-distribution-template-arm64.xml#L4

Perhaps you're trying to install an intermediate pkg artifact which we don't consider a shipping installer?

[AraHaan]

That might be what causing the installers I generate in my codebase which uses arcade to do this.

Here is where I set up those installers specifically: https://github.com/Elskom/runtime/pull/16/files (I was using arcade to learn the whole installer setups that goes into making the shipping installers that the official .NET SDK and the others use)

[marcpopMSFT]

Old issue triage: No plans around this at this time.