elm: add the platform and helpful scripts

[abbradar]

cc @peti -- I haven't integrated this into haskell-modules, instead using overrides to add needed packages. Maybe we want to do this some other way?

TODO:

• Documentation
• A way to package elm modules? (don't see any use case for now)

[peti]

This patch looks fine to me. I wonder about two things:

1. Why don't the packages live underneath pkgs/development/pkgs/development/elm-modules? Putting them underneath the compiler is unusual in Nixpkgs.
2. What is the reason for duplicating Haskell build expressions like elm-compiler rather than using the ones we already have?

[abbradar]

1. This is the Elm platform without any Elm packages in Hackage sense (well, there are technically several packages for elm-reactor, but they are isolated), consisting of a compiler, a REPL, a debugger and Cabal-like utilities -- I felt that this is more a "compiler" than "modules".
2. The upstream has stopped updating Hackage packages and promotes their own build script which checks out specific git tags and builds a sandbox. I'm using a small Ruby script to generate needed packages from their specification. For instance, elm-compiler-0.15.1 is not on Hackage.

EDIT: Elm does have a package library, but I don't see any use case or a way to package it -- it would require changes in their package manager.

[peti]

Thank you for the explanations! I wish the Elm people would deprecate their package on Hackage if they don't intend to maintain it there anymore.

[peti]

Anyway, the code looks fine to me. Merge away if you feel that it's ready. Also, I'm about to push 9e7ce5b to disable the broken Elm variants in the haskellPackages set.

[doshitan]

I came up with my own hack to get the latest Elm stuff before I saw this. Your approach is much better (^_^). My hack is here if you want to take a look. I kept the Elm packages a part of haskellPackages, just providing versions that sourced from GitHub instead of Hackage.

My only suggestion for this pull request is that elm-repl requires both elm-make and nodejs to exist in it's $PATH in order for it to actually work. elm-repl has flags to point it at the specific compiler and interpreter binaries you want to use, but being in $PATH is good enough (it will look for elm-make and node or nodejs binaries to use by default). I just used wrapProgram.

[rehno-lindeque]

@evancz can probably mark the Hackage packages as deprecated

[evancz]

They are all marked as deprecated.

[rehno-lindeque]

Thanks!

[rehno-lindeque]

Also paging

• @agrafix wrt elm-bridge
• @JoeyEremondi wrt elm-core-sources / elm-build-lib
• @JustusAdam wrt elm-init.

I just noticed your packages was also marked broken in 9e7ce5b#diff-8f392bd0e4fd42a66d9e0cd4901ec287R919. Are they deprecated?

I'm sure some of these are still actively maintained on Hackage (not part of the Elm platform). elm-bridge was just announced the other day.

These all depend on deprecated packages, so I'm guessing it's safe to mark deprecated:

• @kylcarte wrt snap-elm (not included in the commit, but is probably broken)
• @tazjin wrt elm-yesod
• @maxsnew wrt hakyll-elm

Please mark as deprecated on Hackage if you don't mind.

[JustusAdam]

elm-init doesn't depend on any elm platform packages.

I personally haven't used any package distribution other than hackage and I'd appreciate if someone could tell me what the canonical way of publishing elm related software is now so I can submit upstream changes to the right place.

[agrafix]

@rehno-lindeque elm-bridge does not depend on any elm platform packages and is not deprecated.

[abbradar]

@peti I believe there was a misunderstanding (correct me if I'm wrong!) -- Elm platform consists only of

• elm-make
• elm-package
• elm-repl
• elm-compiler
• elm-reactor
• Elm (deprecated)
• elm-get (deprecated, too)
• elm-server (deprecated)

Other packages are not in the platform (nor in my PR) and their authors still release them on Hackage.

EDIT: I've looked though now-broken package list. Those packages do depend on elm-compiler and while we don't know what to do with them we may want to leave them as broken:

• elm-yesod

• elm-build-lib

  Also added deprecated platform packages to the list above.

[abbradar]

@doshitan Thanks for your advice! I'll fix this, add some documentation and this should be good to go.

[rehno-lindeque]

@JustusAdam I think it's probably something you can bring up in the elm-discuss mailinglist, we probably want to avoid spamming this PR. (I believe Hackage should be fine as long as you don't depend on Elm platform packages).

[JoeyEremondi]

Sorry for the dealy on my part, I just depricated elm-build-lib, it hasn't
been updated in a while, and I'm not sure if anyone is using it.

On Mon, Aug 17, 2015 at 12:32 PM, Nikolay Amiantov <notifications@github.com

wrote:

Merged #9233 #9233.

—
Reply to this email directly or view it on GitHub
#9233 (comment).