> If your dependency is used by more than one package within the distribution, it should be split out and not vendored... That's like going back to square-one:

> If your dependency is used by more than one package within the distribution, it should be split out and not vendored... That's like going back to square-one: Dependency Hell [1]. That's a regression, not a solution. I believe the problem is not at the edges (OS packaging, software developers), but in the middle: The dependency handling in programming languages. I.e. you need to be allowed to install multiple versions of a library under the same "environment" and activate the version you want at launch time (interpreted languages) or build time (compiled languages). [1] https://en.wikipedia.org/wiki/Dependency_hell https://en.wikipedia.org/wiki/Dependency_hell