homeassistant

hideshow 4 child comments

parent

[–] Strit@lemmy.linuxuserspace.show 19 points 2 years ago (1 child)

You didn't mention in your OP that it had to be debian distro packages. I just gave examples of HA being packaged in other ways than a complete OS.

I could have said: "If you want to run HA from packages, you need to install Arch!" But I didn't. Chill out.

hideshow 2 child comments

parent

[+] rah@feddit.uk [S] -24 points 2 years ago

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

It doesn't. WTF are you talking about?

parent

[–] hendrik@palaver.p3x.de 13 points 2 years ago* (last edited 2 years ago) (1 child)

A lot of software isn't packaged for Debian. Especially complex ones and webapplications tend to be Docker containers or something like that. Home Assistant has a lot of Python dependencies which are a chore to maintain the Debian way. Same probably applies to some other distros. I mean it can be done, as Arch and NixOS show...

And you have Docker, you can install HA core in a Python virtual environment on any distro, or install Supervised, or the appliance (OS).

So there are many ways to install it. And I have the same complaint for other software. For example I'd like Nextcloud and a few other collaboration services to be available as distro packages. Sadly they aren't available like that.

hideshow 2 child comments

parent

[+] rah@feddit.uk [S] -21 points 2 years ago (2 children)

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.

hideshow 4 child comments

parent

[–] 4am@lemm.ee 13 points 2 years ago

You don’t have to use HomeAssistant if you hate it so much.

parent

[–] hendrik@palaver.p3x.de 10 points 2 years ago* (last edited 2 years ago) (1 child)

Yeah, I don't think I agree with you at all. Software development and operation are vastly different jobs. Packaging is yet a different story. Maintainers need different things than developers. Handling dependencies is a chore, and you need lots of them if your product speaks dozens of protocols and can interconnect with thousands of devices, each with their own quirks... All the people have something in mind. 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. There are other factors at play. And sure. It'd be awesome if we solved software packaging, dependency hell, the supply chain of larger projects and everything. It's just not easy. And reality has quite some limitations. It's just... fighting reality doesn't get you anywhere. Sometimes we have to make ends meet with imperfect solutions. Or you just live without a smart home. Or use a different software stack. I mean there is FHEM and some other projects.

And with that said, there is some merit to what you're saying. Software should be designed with usage in mind. It's just not easy and there are contradicting requirements. Either someone puts in all the effort to cater for your specific use-case... Or they don't.