[erlang-questions] Erlang package manager

[Dmytro Lytovchenko]

Going with Nix sets few targets to focus on:
- Adapt it for Erlang specifics (and contribute if they will accept flow of
contributions of this type). If they don't like it, we're facing a source
code fork. It's licence is LGPL2.1(or later) which is sticky and may annoy
people;
- Make it work on Windows;
- Nix is C++ so OTP team will squint at it, they don't like and don't use
C++ but, well, many other people including me do. Besides opensource
contributions, a permanent one or more people should be assigned to
maintain the Erlang-faced part of Nix, that is up to IUG to decide the
budget and the candidate(s), hope i can be one.

Erlang specific details include:
- make it appear (be built or downloaded or bundled with OTP) when you make
OTP source;
- source-only and binary installs being recognized as interchangeable. but
if user is unable to build for some reason he may enforce binary prebuilt
install;
- making environments for Erlang, that is a directory with symlinks to
packages, which can be added to -pa/-pz and starting an OS shell or Erlang
shell for user;
- make it aware of Erlang in general, people will find out what they want
when they start using it. Many surprise things may appear such as hot
upgrades and reloads on a running VM, not sure if that's package manager's
thing to poke VM with a stick and make it reload things.


On Sat, Dec 27, 2014 at 1:48 AM, Imants Cekusins <imantc@REDACTED> wrote:

> Nix package repository is very convenient to search :
>
> https://nixos.org/nixos/packages.html
>
> simple and very fast. It sets a good example.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141227/b20ae4f4/attachment.htm>