this post was submitted on 17 Sep 2024
-6 points (45.0% liked)
homeassistant
14875 readers
5 users here now
Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.
Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation
Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @[email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You should ask this to your favourite distro packagers, not to the home assistant developers.
In any case, it is such a mess of dependencies due to load of optional packages, very active development, that continuously break dependencies on the package repo.
What advantage would bring have a most of the time obsolete distro specific repo? On a maintainer POV this is the typical use case for distro agnostic deployment, maybe flatpak, maybe docker.
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.
What does that mean in the context of Home Assistant?
Since HA depends on a lot of python packages, on external softwares and libraries it could not feasible to ensure that the versions packaged with the distribution will always be in line with those needed by HA
I disagree.
Then go do it.
I'm not a Debian Developer and won't become one: http://settrans.net/~rah/why-not-debian.html
Also, I'm not a Home Assistant user so I've no interest in contributing.
Then do if for your distribution then. It's clearly not that difficult, you've all but explicitly stated as much.
I use Debian.
I have not said that, or anything like it.
Perhaps you missed the fact that I'm not a Home Assistant user and have no interest in contributing?
So then it isn't actually that feasible then, otherwise you'd do more than just whine about it on the Internet. Especially when there are valid reasons to not support that method.
So let me get your logic straight: you're saying that it isn't feasible because if it were feasible then a person who could do it would necessarily do it? LOL that makes no sense.
Well, yeah. Especially when you've already been given reasons why it isn't. But clearly you know better than the devs or people familiar with the product.
Why do you think that because a person could do something they necessarily will?
I don't, but in this case, we know it's not because they got rid of that option. Why? Because the task is infeasible to support. Kinda like you've been arguing against this entire time in the face of multiple reasons why people aren't doing it.
You're far from the first person to want this, and the devs no longer offer it as a supported method for a reason after all. No one is saying it is impossible, just not something that's feasible to create and support. This really should not be this hard of a concept to understand.
You're not making any sense.
Are you saying that the Home Assistant developers used to support distro packages?
OP is saying that. They said it was "infeasible".
Well, good for you. Now let's prove it
You first.
@rah @Zavorra it's easier to build a business model around an OS than it is around a package distro.