hex-ifying erlang packages

[Alex Shneyderman]

Hi, All!

The docs on the topic in the subject are a little sketchy. Could anyone explain to me the steps? There are few scenarios:

1. erlang project owner creates package.exs and maintains that in his own repo of the package. Does the owner need to publish it afterwards or can anyone with the clone of that repo  publish it?

2. Community packages, there is a bunch of those. What are they for? And why would anyone need those in place of 1, especially if package can be published from a clone?

3. Is there a way to test wrapped erlang project, without actually publishing it first?

Thanks for any possible clarifications.

Cheers,

Alex.

[Eric Meadows-Jönsson]

Hi Alex,

1. Anyone can publish a new package. Only owners of a package can publish new versions of an already published package.

2. Community packages are for when you need a package published that you don't own but you don't want to take on the responsibility of maintaining it or publishing new versions of it forever. The problem with 1. is that someone else than the project maintainers may publish the package and then stops publishing new versions for whatever reason, if you need a new version published you would need to publish it as a new package with another name even though it's the same project.

3. No, but we want this functionality for both Elixir and Erlang projects.

--
You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-ta...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-talk/c135b9c3-a957-41b3-a072-d32308615b9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Eric Meadows-Jönsson