Add new comment

if you talk about packages from your distributions repositories (packages built for your distribution and release), because the way packagers solve a dependency problem (new version of library not being backwards compatible) is to support both the old and the new version of the library or to patch the software if it's a simple fix. The real problems exists for third party "package" maintainers, a problem LSB tries to solve in a clumsy and short sighted manner. This package manager tries a different approach to the problem. I don't know about you guys, but I'm not going to be happy if UT2K4 stops working because some library version gets kicked for being deprecated. A solution to the problem could be a secondary package manager supporting any possible version of a library.