rah

the Home Assistant .deb distro package

Firstly, that's a .deb but it's not from a distro. Secondly, that .deb doesn't contain Home Assistant, it contains some "Supervised" which runs the Home Assistant Docker container:

https://github.com/home-assistant/supervised-installer/blob/8dbfda2221b955dc810827285c5ac874eb0b70d9/homeassistant-supervised/usr/bin/ha#L10

LOL

They already pay attention to deployment and support several methods. Sure it's not the method you have in mind. But the world doesn't specifically revolve around you.

It's not my method. Writing software with distributions in mind is the standard in free software development.

It's just not easy.

Indeed. That's why many engineers don't bother. Especially poor engineers.

You should ask this to your favourite distro packagers, not to the home assistant developers.

I disagree. The Home Assistant developers are the ones who chose to create an OS. They could have chosen to create distro packages instead, or at least software which is amenable to being packaged by distros.

obsolete

What does that mean in the context of Home Assistant?

A lot of software isn't packaged for Debian.

Yes, often projects which are engineered without distros in mind. Which is to say, engineered poorly.

You didn't mention in your OP that it had to be debian distro packages.

It doesn't. WTF are you talking about?

That's manual installation which is (a) not distro packages and (b) exactly what distro packages are created to avoid.

docker images

Is not distro packages.

Arch Linux

It's not in Debian. There's no Red Hat packages either. Or OpenSUSE. It's not even in OpenWrt which would make the most sense. So it looks like no useful, practical distro packages.

pip

Is not distro packages.