Support of ubuntu derivatives

Start by reading install.sh and how it derives the platform from /etc/os-release, especially ID, ID_LIKE, VERSION_ID, and UBUNTU_CODENAME. Check the referenced erlef/otp_builds releases while tracing Elixir 1.20.3 and OTP 27 selection; done means Linux Mint and other Ubuntu derivatives can select valid builds or receive a clear supported-version error.

Hi, I'm new to Elixir, and very much interested, including the AtomVM for embedded systems.

I tried to install Elixir on my linux mint machine and I get "linuxmint not supported" as result of the install.sh. I'm not at ease with all the detailed working of shell scripts, so I'm afraid I can't just make a useful pull request, but I was wondering if I could get a working Elixir install (and then AtomVM on ESP32). I see that the install.sh deducts the image name from the version of elixir and otp. Because of teh status of AtomVM,
My os-release is as follows :
NAME="Linux Mint"
VERSION="22.1 (Xia)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 22.1"
VERSION_ID="22.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=xia
UBUNTU_CODENAME=noble

I'm probably not teh only one with the problem, maybe even people using lubuntu or kubuntu would have teh issue !

So at first I thought that replacing "ubuntu" by "linuxmint" in install.sh would solve the problem, but actually the version numbers also differ. Do you think you could solve the problem, for example by looking at the "UBUNTU_CODENAME" instead of the "ID" or "VERSION_ID" ? That looks to me as an elegant solution, but it would only work if ubuntu distributions also have a "UBUNTU_CODENAME.

I need to use elixir@1.20.3 otp@27 but that won't work either ,because (according to a grep on https://api.github.com/repos/erlef/otp_builds/releases , these is no single build left starting with OTP-27 :
"tag_name": "master-latest", "tag_name": "maint-latest", "tag_name": "maint-28-latest", "tag_name": "maint-27-latest", "tag_name": "maint-26-latest", "tag_name": "maint-25-latest", "tag_name": "OTP-29.0.5", "tag_name": "OTP-29.0.4", "tag_name": "OTP-29.0.3", "tag_name": "OTP-29.0.2", "tag_name": "OTP-29.0.1", "tag_name": "OTP-29.0", "tag_name": "OTP-28.5.0.5", "tag_name": "OTP-28.5.0.4", "tag_name": "OTP-28.5.0.3", "tag_name": "OTP-28.5.0.2", "tag_name": "OTP-28.5.0.1", "tag_name": "OTP-28.5", "tag_name": "OTP-28.4.3", "tag_name": "OTP-28.4.2", "tag_name": "OTP-28.4.1", "tag_name": "OTP-28.4", "tag_name": "OTP-28.3.3", "tag_name": "OTP-28.3.2", "tag_name": "OTP-28.3.1", "tag_name": "OTP-28.3", "tag_name": "OTP-28.2", "tag_name": "OTP-28.1.1", "tag_name": "OTP-28.1", "tag_name": "OTP-28.0.4",

I believe that the install script should be tuned to allow to use all these builds, so maybe even maint should start with "OTP-" ? Like "OTP-27-maint" ? Or should I specify something else than otp@27 ?

In any case, thanks in advance for teh attention you'll bring to my issue.