Handling Arch Linux ARM archives for the Raspberry Pi?

• Etcher version: Version 1.5.57 (1.5.57)
• Operating system and architecture: macOS Version 10.13.6 (17G4015)
• Image flashed: ArchLinuxARM-rpi-3-latest.tar.gz
• Do you see any meaningful error information in the DevTools? No

I tried flashing this image, downloaded from the Arch Linux ARM Downloads page. I received the following dialog:

Invalid Image .../ArchLinuxARM-rpi-3-latest.tar.gz is not a supported image type.

I gather that creating a bootable device for Arch Linux is a rather complicated task. According to this HowTo article, it requires more than a dozen sudo commands. So, it’s exactly the sort of problem I’d like Etcher to handle for me. What are the chances of this limitation being resolved?

P.S. I’m not sure how to report this kind of meta-issue, but… This field’s template says: “You can open DevTools by pressing … Cmd+Alt+I if you’re on Mac OS.” The Mac has an Option key, not an Alt key. Also, the name of the operating system is macOS.

[lurch]

as long as there’s something that talks to ext4 in the toolchain

If you want to do some experimentation yourself, https://github.com/balena-io/node-ext2fs might be a good starting point? 🤷‍♂️

[unquietwiki]

• https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3
• https://techcommunity.microsoft.com/t5/Containers/Tar-and-Curl-Come-to-Windows/ba-p/382409

Instructions on Linux at least are to make 2 partitions; one for a FAT32 boot loader; one ext4 to dump the operating system to. Win10 has tar support now; so as long as there’s something that talks to ext4 in the toolchain, maybe it can be automated?