3 ms·
I think this is a widespread problem, especially with things like npm where small modules are advocated for. Taking a random example from GitHub, installing th
by diggan 8y ago
I think this is a widespread problem, especially with things like npm where small modules are advocated for.
Taking a random example from GitHub, installing the npm modules for Polymer/polymer yields duplicate dependencies of @types/node (4.9.1, 6.0.118, 9.6.41, 10.12.18, 10.12.21) dom5 (1.3.6, 1.1.0, 3.0.1) and many more modules...
I'm pretty sure you can find similar examples from most popular open source projects.
- viraptor 8y agoIncluding multiple versions of openssl is not as trivial as adding another dependency in the packages file. It actually takes a bit of effort / linker fun to include multiple versions without a conflict. It also takes a special kind of person to both be capable of this and not realise this shouldn't be done.
- twic 8y agoMy guess would be that the firmware includes multiple binaries which run as separate processes. If there are 70 tools which speak SSL, it wouldn't be a huge surprise if there were 70 copies of OpenSSL.
- yjftsjthsd-h 8y agoYeah; it's kind of impressive, in a way. It reminds me of my reaction when I first found out that Mac OS / Darwin's kernel was built by taking Mach and then grafting parts of BSD on top: "Wait, you can do that!?"