Hacker News new | ask | show | jobs
by acabal 5203 days ago
Firefox is a special case. Ubuntu specifically updates that one package more frequently. Perhaps it was a bad example as that's one of the very few packages that is singled out for frequent updates by Canonical.

PPAs still aren't the best solution even if distros make them easy-to-use. The reason is that now maintainers have to get their software into two places: the core repos and now an optional up-to-date PPA. Additionally they must still target those PPAs to every single new version of the entire distro. For example: I run Natty because I like Compiz, but Oneiric has showstopper Compiz bugs for my ATI card. On Natty I use a PPA that downgrades the version of Compiz to a more stable one. However that PPA has not published an update for Oneiric, so I can't upgrade to Oneiric and get other new packages. What now? My fate is in the hands of a single PPA maintainer.

Or: many PPAs only publish releases for the past 2 or 3 distro releases. What if I'm on a non-LTS release and don't want to upgrade (because upgrading would bring in more unwanted packages), but the PPAs I use no longer publish for my version? I'm out of the game again.

The core problem in these scenarios is the distro model. Devs have to keep their apps up to date with the quickly-moving target of a "distro." That's just not a situation anyone should be in. The OP and the linked article explain this better than I can.

1 comments

You want stability and a slowly-changing core system, but won't use the LTS releases? Because your app provider doesn't make updated PPA's for the LTS release. At which point you blame the existence of the distro's non-LTS releases? I think the correct target of your ire should be the app developer who doesn't produce PPAs for the LTS release.

I carefully read what you wrote, and IMHO your requirements are not reasonable: in effect, you want the non-LTS releases of distros to vanish so that app providers don't have the temptation to not support previous releases.

Maybe I'm a what somebody called a "technologist" downthread.

I want what Windows does: Stable core, independent apps. The entire concept of "LTS" is a red herring. It's a byproduct of the distro mindset. To put it another way: There is no Windows LTS. You buy one version of Windows and it works for a decade--a DECADE--and your apps are kept updated for as long as the developer cares to do so, often automatically in-app. (There's no Windows "app store", but as Apple demonstrates it's a matter of will, not technology, to make one.)

That is simply not the case with Linux today no matter how you frame it. And for some reason too many Linux supporters are totally blind to that because they think package managers are flawless gems of convenience. They mistake package managers for convenience when in reality they're a band-aid for a situation that shouldn't exist in the first place, and that other OS's have solved better. The OP calls this out perfectly.

Please do not blame "package managers": Windows Installer is a package manager in many ways comparable in scope to dpkg, which given your premise immediately disproves that they are the cause of the problem you are talking about; the issue is not package managers, it isn't even centralized package distribution systems like APT: it is that the ecosystem of libraries and protocols that make up the Linux desktop have horrible binary compatibility issues that distributions seem to make even worse through the usage of "rebuild the world and update all the dependency relationships while we are at it" policies.