Sean Russell wrote:


> I want the following features in a distribution mechanism:


Will this take care of conflicts?

If app A needs lib Foo version 1, and the newly installed app B runs 
with lib Foo version 2, then will satisfying B's dependency (lib Foo 2) 
break app A? I think a packaging mechanism should be able to deal with 
backwards incompatible versions of shared libs; app A uses Foo 1, app B 
uses Foo 2, so all dependencies are resolved, without breaking stuff by 
introducing conflicts by updating libs.
To uniquely identify libs, URIs might be helpful.

Tobi


-- 
http://www.pinkjuice.com/