为什么Erlang没有像宝石一样的包装管理系统？ [英] Why doesn't Erlang come with a decent package management system like gem?

问题描述

好的，这听起来有点恶心，但是我想知道是否有技术原因Erlang默认没有一个正确的包管理系统。

Ok, this sounds like a bit of a rant, but I was wondering if there was a technical reason that Erlang doesn't have a proper package management system by default.

推荐答案

真的没有重大的技术原因。只是不同的需求，因为设计和安装erlang软件的经典方式是应用程序。还有一些使用版本添加到这个。

No major technical reason really. Just different needs as the classic way of setting up and installing erlang software is though applications. And some use releases added to that.

通常你看到erlang软件完全自发分配。也就是说，它将所有的库和虚拟机都包在一起，而不需要任何外部依赖。你甚至可以在包的开发版本中看到这一点。例如，Riak数据库的源代码树中有所有依赖库。

Often you see erlang software distributed completely self reliant. That is that it contains all the libraries and the virtual machine together in a package and not needing any sorts of external dependencies. You even see this in development versions of packages. The source tree of the Riak database for example has all dependent libraries in it.

这不是一个坏主意，像许多来自Ruby的人（像我一样）可能会想。这样每个应用程序都是自力更生的。由于Erlang的主要目标之一是成为可靠的最可靠的东西，因此每个应用程序都可以拥有它自己的库的版本，这使得世界各地都有意义。因此，确保一个应用程序不会使其他应用程序不稳定。

This is not a bad idea like many coming from Ruby(like me) may think. This way each application is self reliant. As one of Erlang's main goals is to be the most reliable thing available it makes every sense in the world that each application can have it's own version of the library. Thus making sure one app does not make the other unstable.

这篇关于为什么Erlang没有像宝石一样的包装管理系统？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！