Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even if you just use 2 apps that depends on 1 library, there may be tens or hundreds of such apps in the distribution repository (which is, btw, the case for libgmp). A bug in such library would force distribution maintainers to release new packages for all these applications, instead of just one.

I think that if the library is independent upstream project, then there is no reason why it should not be dynamically-linked independent package in distributions.



> A bug in such library would force distribution maintainers to release new packages for all these applications, instead of just one.

Surely that's automated?


> Surely that's automated?

Doesn't matter. You'd rather update X separate packages (of unknown size & potentially different maintainers or update policies) to fix 1 bug in a library they all happen to use?

Shared libraries are a good thing, period. Implemented poorly? Fix that instead, rather than include everything & the kitchen sink in every single app.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: