I think this mostly works OK except for one area: package format. The disparate package management in Linux is indefensible because it weakens the entire development ecosystem. One thing that hugely hurts the package management in Linux is that package format disparity means that the tooling for package management is far inferior to what it could be. The Linux package managers could be the single greatest tool for developers, but instead we have increased fracture over the entire ecosystem.
One of the biggest problems is the inability for the package managers to integrate with language-specific packages. Gem/pip/cabal cause an extremely obnoxious fracture because they all have dependencies which can't be tracked without an OS package manager but at the same time the OS package manager can't integrate with them. If Linux could decide on a single package format and packaging tool then we could all start working on tooling to support integration of the different language packages. However, as long as there are still 3-4 major package formats and packaging tools that's not going to happen.
Added to that are the package managers reliance on specific OS constructs. Homebrew works but we really shouldn't have to use different package managers just because we're on a different operating system. Either the package supports that OS or it doesn't, but this shouldn't say anything about the package manager.
Aside from all of this is the difficulty in actually constructing the packages. Arch PKGBUILDs seem the closest I've used to an easy source->binary package but they're not mainstream. As far as I know debs still don't support natively bundling the source with the binaries and the RPM SPEC system is the single unfriendliest system I've encountered to quickly make a portable package. Moreover, the ties to shell script just continue to harm OS independent adoption.
I'm not sure what the answer is but I'm starting to think the only acceptable solution is a complete severing of Linux distributions with package management.