Open gleber opened 8 years ago
I've redone https://github.com/rebar/rebar3/pull/982 according to owners of rebar3, waiting for feedback.
Tooling for this will be placed in: https://github.com/erlang-nix
Here are various changes to the tooling from last week:
https://github.com/NixOS/nixpkgs/pull/12429 https://github.com/NixOS/nixpkgs/pull/12444 https://github.com/erlang-nix/hex2nix/pull/6 https://github.com/erlang-nix/rebar3-nix-bootstrap/pull/1 https://github.com/erlang-nix/rebar3-nix-bootstrap/pull/2 https://github.com/erlang-nix/nixpkgs/pull/2
(triage) @gleber any update?
Closing because of inactivity.
@rasendubi let's not close meta issues. We can't expect people just deliver code every week or month.
@domenkozar, no problem. I've closed because the issue hasn't been updated for ~9 months - seems like nobody cares about it and the work is abandoned. I would be glad to be proven wrong.
Updates which I have forgotten to link to this issue:
Current rough plan of actions is outlined in this comment: https://github.com/NixOS/nixpkgs/issues/26279#issuecomment-313846466
I'm also going to add the following PR's to this list.
@ankhers Thanks for linking to those PRs which I've missed.
I've updated the issue main text with current status and future plans.
I will start working on the common library and the mix2nix plugin.
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
I am starting this issue to track progress of the effort started in #11651. I will be updating this issue with further developments and my implementation plans. If someone wants to jump in and work on it, please let me know (here or privately) to avoid work duplication.
Assumptions
I am working on getting Erlang packages into Nix. The approach is similar to what is done for Haskell. Here are main points:
Current status (2017-09-24)
The following basic features are implemented already:
fetchHex
automates fetching packages from Hex.pm CDNbuildHex
which automates definition of Erlang packages to be fetched and built from Hex.pm CDNbuildMix
to build Mix packagesrebar3
is one with applied patch which makes it hermetic (forbids any attempts to download stuff from the internet)rebar3-open
which is unmodified version of rebar3nix-shell -A erlangPackages.lager.env
) #11818hex2nix
automates creation ofpkgs/development/erlang-modules/hex-packages.nix
file based on hex.pm registry, which includes all buildable versions of packages, including multiple versions of the packagesdoc/erlang-users-guide.xml
contains documentationRebar3 depends on a concept of registry, which is usually fetched from S3. I've created a separate github repo in which I plan to snapshot that single file from S3. This is automated in https://github.com/erlang-nix/hex-pm-registry-snapshots/blob/master/update.sh
Further work
Short term
Long term
Support for
nix-env
Support for
nix-env
has been discouraged by @peti and @domenkozar as unsustainable and giving very little benefits.