This problem in various forms has been around for decades now. In 2007 it was clear to me that Debian style packaging was insufficient for handling anything bey

This problem in various forms has been around for decades now. In 2007 it was clear to me that Debian style packaging was insufficient for handling anything beyond trivial deployments of any tools or services from the Python, Ruby, and Java ecosystems. Things have only gotten faster-churning and more complex since then. The old model of packages for shared libraries that are updated across the board just isn’t workable. Both from the packagers point of view, because of the busywork, but also from the users’ point of view, since the low package coverage means many things just haven’t been packaged anyway. In my opinion it’s probably fine for Debian to stick to the old model still for the core OS features, but operators need to know when to use something different for their own needs.