Package Details: elm-platform 0.19.0-1

Git Clone URL: https://aur.archlinux.org/elm-platform.git (read-only, click to copy)
Package Base: elm-platform
Description: Bundle of all core development tools for the Elm language.
Upstream URL: http://elm-lang.org
Keywords: elm language programming
Licenses: BSD3
Conflicts: elm-platform-bin, nodejs-elm
Submitter: Luchs
Maintainer: None
Last Packager: Luchs
Votes: 18
Popularity: 0.000000
First Submitted: 2015-11-20 13:48 (UTC)
Last Updated: 2018-08-21 18:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

mattjbray commented on 2016-06-13 09:00 (UTC)

I ran into the "allow-newer" problem (now fixed - thanks), now I'm banging my head against: cabal: The following packages are likely to be broken by the reinstalls: ... Use --force-reinstalls if you want to install anyway. Upstream's policy is "Elm 0.17 is just meant to be built with 7.10" (https://github.com/elm-lang/elm-compiler/issues/1397). In the end I had success building Elm with stack: https://github.com/mattjbray/arch-pkgbuilds/tree/master/elm-platform-stack Happy to upload that to the AUR if anyone wants it, but I'm not sure what the policy is on having multiple versions of the same (built from source) package. Equally happy (but not presuming!) for this AUR package to adopt the elm-platform-stack build method.

Luchs commented on 2016-06-12 20:35 (UTC)

There are official binaries available via npm. There is an AUR package for that as well (nodejs-elm), but it's not maintained anymore.

pepper_chico commented on 2016-06-12 20:12 (UTC)

It would be nice if there were a bin version. Build Haskell stuff takes too much time...

Luchs commented on 2016-06-12 14:05 (UTC)

Thanks, I added that.

doodad commented on 2016-06-12 12:42 (UTC)

I had to add echo "allow-newer: aeson,base,HTTP,time,transformers" >> cabal.config before 'cabal update' on the PKGBUILD as per https://github.com/elm-lang/elm-compiler/issues/1397 for me to get the build working.

Luchs commented on 2016-06-10 15:14 (UTC)

Did you do a clean build or did you upgrade from 0.16 in the same directory? Both the upgrade and the clean build work for me here. `--force-reinstalls` sounds somewhat dangerous and the official build script does not include it.

dave_v commented on 2016-06-07 07:07 (UTC)

The build failed for me. Had to add "--force-reinstalls" to the cabal install calls to get it working again. Can you patch the PKGBUILD to do this? Cheers

Luchs commented on 2016-05-11 17:33 (UTC)

No clue about that error, sorry. You could try again now with 0.17 or alternatively install the binaries from node.js. (Sorry, I forgot about your comment.)

mzimmerman commented on 2016-02-06 14:48 (UTC)

Had an error trying to build this: (no experience with elm) Packages configured successfully! elm-make: elm-stuff/packages/elm-lang/core/3.0.0/src/Graphics/Element.elm: hGetContents: invalid argument (invalid byte sequence) elm-make: thread blocked indefinitely in an MVar operation Custom build step: creating and collecting all static resources cabal: Error: some packages failed to install: elm-reactor-0.16 failed during the building phase. The exception was: ExitFailure 1 ==> ERROR: A failure occurred in build(). Aborting...

Luchs commented on 2015-11-27 23:36 (UTC) (edited on 2015-11-27 23:37 (UTC) by Luchs)

I updated the checksums. Apparently, upstream did some fixes and reused the 0.16 tag for those repositories.

« First ‹ Previous 1 2 3 4 5 Next › Last »