Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lfe: 1.2.1 -> 1.3 #40785

Closed
wants to merge 1 commit into from
Closed

lfe: 1.2.1 -> 1.3 #40785

wants to merge 1 commit into from

Conversation

yurrriq
Copy link
Member

@yurrriq yurrriq commented May 19, 2018

Motivation for this change

Hack together an lfe_1_3 derivation and make it the default lfe.

Notably, the following now works.

(include-lib "lfe/include/clj.lfe")
(-> 2 (+ 2) (== 4)) ; true
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@yurrriq
Copy link
Member Author

yurrriq commented May 19, 2018

/ping @ankhers

@xeji
Copy link
Contributor

xeji commented May 19, 2018

Why do we need to keep the old version?

@yurrriq
Copy link
Member Author

yurrriq commented May 19, 2018

We keep old versions of other BEAM languages because many people still use them. In the case of LFE, there aren't very many users, especially on Nix, so it's more for uniformity across BEAM packages than anything else.

lfe_1_2 = lib.callLFE ../interpreters/lfe/1.2.nix { inherit erlang buildRebar3 buildHex; };
lfe_1_3 = lib.callLFE ../interpreters/lfe/1.3.nix { inherit erlang buildRebar3 buildHex; };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need both lfe_1_2 and 1.3? The rule of thumb is, that we usually do this for projects where multiple maintained major versions exists. This seems not the case here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see Q+A above 😃

@Mic92
Copy link
Member

Mic92 commented May 19, 2018

@yurrriq I suppose the older erlang versions are still maintained upstream and only major versions are kept. I am not familiar with LFE, will older versions still receive updates? Were there breaking changes in the last minor release? lfe/lfe@v1.2.1...v1.3

@yurrriq
Copy link
Member Author

yurrriq commented Nov 26, 2018

I really don't use LFE anymore, so I'm not motivated to get this working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants