Possibility of re-using release names of underlying Ubuntu Distro

[spotlesscoder]

What Happened?

Quite a lot of install scripts of popular software / developer tools fail when running them on elementaryOS
For example, when installing the Azure CLI package repository with the script provided by Microsoft, this ends up in the apt source definition
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

cat /etc/apt/sources.list.d/azure-cli.sources

Types: deb
URIs: https://packages.microsoft.com/repos/azure-cli/
Suites: jammy
Components: main
Architectures: amd64
Signed-by: /etc/apt/keyrings/microsoft.gpg

When running apt update, this of course does not work for this repository as the package is only provided for the Ubuntu release name jammy etc.

Same for curl https://get.docker.com | sudo sh

Steps to Reproduce

Run the installation script as shown above

Expected Behavior

The point where most of the scripts pull their release name info from should contain the release name of the underlying Ubuntu distribution rather than the elementaryOS release name

I don't know what implications this would have for other aspects but if it is feasible, the current behavior of elementaryOS in this regard should be changed

Host OS

ElementaryOS

Image Version

7.1, 8.0

Hardware Platform

64-bit AMD/Intel (x86)

Log Output

n.a.

Hardware Info

No response

[stsdc]

Aren't there any legal implications, if we're just start using other distros names?
Shouldn't third party adapt to the OS and not vice versa?

[spotlesscoder]

I cannot say anything about the legal implications
While it would of course solve the actual problem if software vendors would treat the horus and other elementaryOS release names similar to its underlying ubuntu version - this simply would not be feasible for a lot of distros because how would a software vendor know all release names of any distro that is out there - elementary is probably one of many distros out there having different release names

[danirabbit]

Docker for example does include some specific directions for other (non-Ubuntu) Linux distros: https://docs.docker.com/engine/install/#other-linux-distributions

There is an upstream flag in LSB release that scripts can use. This is also used by Mint for example: https://askubuntu.com/questions/926049/using-ubuntu-derivatives-and-ubuntu-how-do-i-get-the-ubuntu-codename

Generally, don't run scripts unless you totally understand the full contents. But this is pretty much a solved problem already