Yep, believe it or not, it’s probably the most stable rolling release distro out there. I’ve used it for the past 4, 5 years or so, not once has it broken.
There are 2 main reasons why this is. One, they don’t roll with bleeding edge, they opt for stable, so cutting edge is more like it. And two, they don’t have something like the AUR. There is only the main repo and that’s it. The approval process for new packages is quite strict and it has to fulfil a lot of requirements, among which the software has to not just build, but also run on i686, x86_64, ARMv5/6/7 and ARM64. And not just on glibc, but also on musl. So basically, all that, times 2. Sometimes it may take up to a year to get new packages approved by the maintainers, depending on how big the package is and how integrated in the system it is.
The word “stable” usually means unchanging through a release. I.e. functionality of one release is the same if you stay in that release even if you update (security and bug fixes mostly). The experience of the system not doing anything unexpected like crashing is reliability. A rolling distro is by that definition not stable, but it can be more or less bug free and crash free.
No, it doesn’t the only unchanging distro is debian, and they do it mostly out of resourse constraints not because it is a good idea.
Like the only lts package that debian does update is linux kernel. Everything else is patched for vulnerabilities at best, left to rot as stable as a rule.
A bold claim. RHEL updates are mostly security patches, are they doing that due to lack of resources too? Is it that hard to imagine that enterprise distros don’t want surprises from changing functionality?
Yes. Independent, rolling, stable.
Huh?
Yep, believe it or not, it’s probably the most stable rolling release distro out there. I’ve used it for the past 4, 5 years or so, not once has it broken.
There are 2 main reasons why this is. One, they don’t roll with bleeding edge, they opt for stable, so cutting edge is more like it. And two, they don’t have something like the AUR. There is only the main repo and that’s it. The approval process for new packages is quite strict and it has to fulfil a lot of requirements, among which the software has to not just build, but also run on i686, x86_64, ARMv5/6/7 and ARM64. And not just on glibc, but also on musl. So basically, all that, times 2. Sometimes it may take up to a year to get new packages approved by the maintainers, depending on how big the package is and how integrated in the system it is.
The word “stable” usually means unchanging through a release. I.e. functionality of one release is the same if you stay in that release even if you update (security and bug fixes mostly). The experience of the system not doing anything unexpected like crashing is reliability. A rolling distro is by that definition not stable, but it can be more or less bug free and crash free.
No, it doesn’t the only unchanging distro is debian, and they do it mostly out of resourse constraints not because it is a good idea. Like the only lts package that debian does update is linux kernel. Everything else is patched for vulnerabilities at best, left to rot as stable as a rule.
A bold claim. RHEL updates are mostly security patches, are they doing that due to lack of resources too? Is it that hard to imagine that enterprise distros don’t want surprises from changing functionality?