[erlang-questions] Erlang package manager

Dmytro Lytovchenko <>
Wed Dec 17 10:47:18 CET 2014


They way Nix does that (simplified estimation) -- is that it stores all
package versions in its cache, and when you need a shell with specific
versions of packages, it resolves versions and starts a shell for you with
paths adjusted in such a way that you only see versions requested. I can
see this as running "$ erlangpackagemanager shell" or alternatively it may
print paths to copy-paste to your -pa or -pz (not to be committed to git as
those paths will be local, of course).

On Wed, Dec 17, 2014 at 9:49 AM, Loïc Hoguin <> wrote:
>
> On 12/17/2014 02:18 AM, Tristan Sloughter wrote:
>
>> * No global install
>>
>> It just causes headaches. Sandboxes are much more fun to play in without
>> all the kids in the neighborhood crowding in and someone ending up
>> leaving a poop in it.
>>
>
> I think this is a very important point. I like deps not because I enjoy
> compiling everything, but because they are local to the project and I can
> have different projects use different dep versions without having to worry
> that the wrong version gets picked up.
>
> I am not even sure how -pa or ERL_LIBS work when you have both app-1 and
> app-2 in your lib directory. Which one does it choose? Will it choose the
> right version when I want to start a shell for experimenting? I have not
> seen anything that allows me to choose what version to run outside of
> making a release/upgrade.
>
> --
> Loïc Hoguin
> http://ninenines.eu
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141217/636356ce/attachment.html>


More information about the erlang-questions mailing list