[erlang-questions] Erlang package manager

Loïc Hoguin essen@REDACTED
Mon Dec 22 12:36:04 CET 2014


Adding something I believe nobody mentioned yet (if I missed it, sorry).

The way things are now there are many companies or larger projects who 
have a fork of some of the projects they use, because they need a 
specific set of patches on top of them (sometimes these can easily be 
contributed back; but sometimes they are plain hacks).

The package manager should be able to handle this, perhaps by allowing 
some package information to be overriden to allow changing the source 

Another solution could be to allow applying a set of patch files.

None of this would apply to binary-only packages though, of course.

On 12/16/2014 01:41 PM, Bruce Yinhe wrote:
> Hi everyone,
> Industrial Erlang User Group (IEUG) has been working together with the
> Erlang/OTP team to investigate and create a package management system
> for Erlang/OTP.
> The lack of a package management system for Erlang has been discussed
> for a long time in the community. In essence, a straightforward package
> management system is believed to take Erlang programming language a step
> forward. Multiple tools will appear in the community. It needs to be
> supported by a highly visible community behind it.
> In order to increase the adoption and to result in a tool widely used in
> the Erlang ecosystem, we are identifying the most important user
> categories and use cases, based on what the majority of the community
> want in a package manager. Therefore we would like to invite an open
> discussion.
> Now you are welcome to share your thoughts, suggestions or proposals
> about an Erlang package manager. It would be great if you could reply
> with your motivation, explaining why a feature is necessary to have.
> There are some example questions to begin the dicussion with, including,
> but not limited to the following.
>   * What metadata information should an Erlang package include?
>   * What functionality do you need in a package manager for Erlang in
>     order to use it in production?
>   * What other concerns do you have about an Erlang package management
>     system?
> Erlang package manager's brief wish list of features:
>   * Console interface
>   * Web interface
>   * Package Index and Repository
>   * Fetch, Install and Remove Packages
>   * Publish packages
>   * Versioning and Dependency Management
> We are aware of several previous efforts and existing tools that attempt
> to achieve the similar goal. We want to look at existing things, both
> from Erlang and Elixir, to see if they fit the requirements. If not, we
> will then have to make something new, perhaps as a rewrite of an
> existing tool.
> The IEUG members are putting together requirements for a package manager
> and will work with the community and Ericsson to create a standard and
> address any voids which exists in the existing tooling, funding
> necessary efforts required.
> Best regards
> Bruce Yinhe
> Erlang Community Manager
> Industrial Erlang User Group
> community-manager@REDACTED <mailto:community-manager@REDACTED>
> +46 72 311 43 89
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

Loïc Hoguin

More information about the erlang-questions mailing list