Skip to content

Conversation

@ee7
Copy link
Member

@ee7 ee7 commented Aug 22, 2023

Allow fetch-configlet to:

  • download the existing riscv64 Linux asset
  • support future assets for e.g. FreeBSD/NetBSD/OpenBSD
  • support low-priority, but theoretically possible future assets for powerpc/powerpc64/powerpc64le/sparc64/etc

Working towards my suggestion in #805:

I think we shouldn't hardcode the available binaries in the fetch scripts. Instead, we should try to download the configlet release for the user's machine, and error if the asset does not exist. Then we can add assets to the configlet releases without updating the fetch scripts on every track. That'll also make the fetch script support riscv64 Linux.

@ee7 ee7 marked this pull request as ready for review August 22, 2023 11:00
@ee7 ee7 requested a review from ErikSchierboom as a code owner August 22, 2023 11:00
Comment on lines +29 to +30
aarch64|arm64) arch='arm64' ;;
x86_64) arch='x86-64' ;;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
aarch64|arm64) arch='arm64' ;;
x86_64) arch='x86-64' ;;
aarch64|arm64) arch='arm64' ;;
arm*) arch='arm' ;;
x86_64) arch='x86-64' ;;

Maybe.

@ee7 ee7 force-pushed the fetch-configlet-more-platforms branch from e2f9960 to 13bb39c Compare August 22, 2023 11:43
ee7 added 3 commits August 22, 2023 13:56
For example, this would work for these `uname -s` outputs:

- FreeBSD
- NetBSD
- OpenBSD
Configlet may never have releases for these. But it's one of the main
remaining architecture names that we'd upload with different names than
the `uname -m` output.

Add support for them now, to avoid an extra Exercism-wide PR for the
fetch scripts later.
@ee7 ee7 force-pushed the fetch-configlet-more-platforms branch from 13bb39c to b3d4707 Compare August 22, 2023 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants