3 ms·
> Personally I believe that vendoring is just the lazy approach by developers that do not want to care about the eco system their software runs in. I have to a
by zozbot234 6y ago
> Personally I believe that vendoring is just the lazy approach by developers that do not want to care about the eco system their software runs in.
I have to agree. If your dependency is used by more than one package within the distribution, it should be split out and not vendored - ultimately, this will reduce the total workload on package maintainers.
This however does not mean that distros should be splitting every dependency into a separate package by default, much less have a separate package in the archive for each build configuration - there's no need to litter the distribution repo with idiosyncratic packages that will never have more than a single project/app/library depending on them, and that's precisely where a vendoring/bundling focused approach might be appropriate. Such dependencies are more like individual source-level or object files, that have always been "bundled" as part of a self-contained application.
- Blikkentrekker 6y agoThe problem is that in the real world despite promises of semantic versioning, breaking often occurs which makes it impossible for two packages to depend on the same version of another library though in theory they should.
- ernesth 6y agoDebian used to manage and package programs from the real world. It is obviously easier to create breaking changes that will not be discovered in dynamic languages. But in the real world, where everybody do unit tests, it is difficult to understand what kind of new problems were not already encountered 20 years ago.
- Blikkentrekker 6y agoWell Rust and npm happened in that time. I don't have much experience with the latter but I know of the former that despite promises of semantic versioning, it is quite common for a crate to not work with a newer version, requiring one to hard depend on a specific version. Add to that that Rust's definition of “non-breaking change” in theory can include changes that A) read to compilation errors or B) compile fine but lead to different behavior.
- m000 6y ago> 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
- zozbot234 6y agoDependency hell is a result of not using sensible semantic versioning. If libraries are properly versioned, it's easy to make sure that each dependency uses the latest compatible version.