aarch64 and arm64 selectors behave differently

[janjagusch]

According to the documentation they should behave identically:

aarch64, arm64 64-bit Arm (these are the same but are both supported for legacy)

But they don't.

With the aarch64 selector the source is found.

  - if: linux and aarch64
    then:
      url: https://github.com/coder/code-server/releases/download/v${{ version }}/code-server-${{ version }}-linux-arm64.tar.gz
      sha256: 13eb5e281c93080a5a0cbb807892e675d98e9ccd5144a9d4dd39533977b94a32
      target_directory: code-server

╭─ Fetching source code
│ │ Fetching source from url: https://github.com/coder/code-server/releases/download/v4.100.2/code-server-4.100.2-linux-arm64.tar.gz
...

link

Wit the arm64 selector the source is not found.

  - if: linux and arm64
    then:
      url: https://github.com/coder/code-server/releases/download/v${{ version }}/code-server-${{ version }}-linux-arm64.tar.gz
      sha256: 13eb5e281c93080a5a0cbb807892e675d98e9ccd5144a9d4dd39533977b94a32
      target_directory: code-server

╭─ Fetching source code
│ │ No sources to fetch

link

Ref.: https://github.com/conda-forge/code-server-feedstock/pull/116

[wolfv]

Yeah indeed, we inherited the way that conda-build does this and use linux + aarch64, and win + arm64 / osx + arm64 … it's a bit unfortunate. We could either adjust our code or the docs I guess.

[janjagusch]

Yeah indeed, we inherited the way that conda-build does this and use linux + aarch64, and win + arm64 / osx + arm64 … it's a bit unfortunate. We could either adjust our code or the docs I guess.

@wolfv, updating the docs would be completely fine for me.