No, and there really isn't any need for it. We're drowning in package managers now and don't need any additional ones at the distro levels (
NOTE: Here's a full list of package managers for most Unixes, titled:"List of software package management systems".
Most programming languages have their own module/library/package managers by the way, there isn't anything inherently special with
Languages and their package managers
- Perl - cpanm, cpanplus, cpanm
- Ruby - gems
- Python - pip
- Node - npm
- R - install.packages()
- the list goes on and on.....
Incidentally, managing software at the OS'es distribution level is actually a passe way to do so. Take a look at tools such as
Renv (R), etc....
I've written up answers extensively on this site about these tools feel free to check out my back catalog of answers.
The OP asked the following follow-up question in the comments.
I use pip and npm on a regular basis, pip almost exclusively with virtualenv. Sometimes luarocks, too. The question isnt so much about their existence. I'm more wondering if a distro maintainers would benefit from existing, prepackaged software libraries in language specific repos.
To which I replied:
I would say, probably not to that point. As you can see from my answer above, there is already a lot of investment in these alternatives, and adding a lang. specific one would just make it more complicated than it already is, for little upside from the package maintainers perspective. I suspect that you're asking this b/c from your perspective it would seem easier for a distro to just tap into a pre-existing library of pre-build packages, however this would then require the distro to tap into a variety of languages libraries.
So you'd be attacking the problem at level where there's an impedance mismatch between the level that the distro needs to be maintained, vs. the level at which the pre-built packages/libraries for a given language can provide.