You are viewing a single thread.
View all comments
5 points

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.

permalink
report
reply
-9 points
*

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?

permalink
report
parent
reply
1 point
*

It seems to me they chose to provide a platform that vastly simplifies the installation of their software and maintenance of its code from a debugging standpoint. This seems perfectly reasonable. This appears to bother a particular community who feel entitled enough to demand multiple developers cater to their distribution’s needs. Shit needs to stop.

permalink
report
parent
reply
0 points

This appears to bother a particular community who feel entitled enough to demand multiple developers cater to their distribution’s needs.

Your reading of the situation is wrong.

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply
1 point

it could not feasible

I disagree.

permalink
report
parent
reply
3 points

It comes down to what are the developers willing or able to support.

For smaller teams they usually don’t want the responsibility of maintaining the package for distros, and HA developers have chosen to not support that option themselves. In their case I see it - what’s the benefit or incentive to them to maintain packages and the associated support costs or headaches. Containers mean they get a known state and don’t have to try to support unknown environments.

Some interested people can maintain the packages for their chosen distro - for instance I see one for Gentoo but it’s only up to 2024.6. It’s the first that came up in a search but there are likely more too supported by the community.

In my case, I also think that using HAOS on a dedicated box has led to a more stable experience as it’s not competing for resources on my other hosts, and attaching devices to it is much simpler. I think encouraging a solid base for people means a better experience overall when to be honest it’s hard to get started with it to begin with for many people.

permalink
report
parent
reply

homeassistant

!homeassistant@lemmy.world

Create post

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

Community stats

  • 669

    Monthly active users

  • 198

    Posts

  • 994

    Comments

Community moderators