[erlang-questions] Erlang package manager

[Leonard Boyce]

Hi Bruce,

Glad to hear there will at least be "official" work effort expended on this.

A few things I'd like to see:
- Require semver for all packages in the index
- Add/remove alternative package locations
- The ability to 'pin' a package in your local system to a specific version
- Options for both local and global install locations (ala deps vs lib
install location)
- Support for both 'archive' and 'source' versions of packages (user option)
- Package signing with signature verification
- Ability to mirror the package index and sources
- All package should have explicit license information and as a user I
should be aware of/have to explicitly accept licenses before any
package is installed

Kind regards,
Leonard


On Tue, Dec 16, 2014 at 6:41 AM, Bruce Yinhe
<community-manager@REDACTED> 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
> +46 72 311 43 89
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>