>First of all, this is the job of the system packager, not the app dev. Second of all, major
>have package dependencies with automatic resolution these days. I know on my system it is
>'yum update firefox'. Why is it better to have a dedicated application installer pulling in
>/usr/local/lib/libpng.so and having the dependency resolver pull in an update to libpng?
Why do we even have a system packager?
It's a source of contention, say you just released important update 1.4.0, but no users can get
And you have no control of when they get it. It may even be they never get it, because the
think it's too big a change.
Every software must be packaged N times for N distros, and the system packager will always
say "NO!" to any 1.2->2.0 update for a stable dist. Even if the developer want it and some of
the users wan't it.
For a (private) laptop user and the app developer it's a mess. The the distro in complete
of your laptop, but nobody really needs that. But the the current complete control/handling of
your system is only great for admins who wan't to control a multiuser system or a webserver.
The point of a self-controlled application is being able to update the actual app, not libpng.
cares about libpng. And it's better because the app developers is in control of their own app
and in direct contact with it's users.
PS: Anything that requires the terminal is not a real solution for 95% of the world ;)