ANN: stack-0.1.4.0 (and 0.1.4.1)

[Emanuel Borsboom]

See README for installation and upgrade instructions.

Note: while stack-0.1.4.1 is on Hackage, the only change is to a comment so that stack’s haddocks build. Therefore, no new binaries were generated. Functionally, v0.1.4.0 is identical to v0.1.4.1.

Note: we have stopped uploading new versions to the Fedora 20 repository, since that version of Fedora has reached end of life. If you are using Fedora 20, use stack upgrade or download the general Linux binary.

Major changes:

• You now have more control over how GHC versions are matched, e.g. “use exactly this version,” “use the specified minor version, but allow patches,” or “use the given minor version or any later minor in the given major release.” The default has switched from allowing newer later minor versions to a specific minor version allowing patches. For more information, see #736 and #784.
• Support added for compiling with GHCJS
• stack can now reuse prebuilt binaries between snapshots. That means that, if you build package foo in LTS-3.1, that binary version can be reused in LTS-3.2, assuming it uses the same dependencies and flags. #878

Other enhancements:

• Added the --docker-env argument, to set environment variables in Docker container.
• Set locale environment variables to UTF-8 encoding for builds to avoid “commitBuffer: invalid argument” errors from GHC #793
• Enable translitation for encoding on stdout and stderr #824
• By default, stack upgrade automatically installs GHC as necessary #797
• Added the ghc-options field to stack.yaml #796
• Added the extra-path field to stack.yaml
• Code page changes on Windows only apply to the build command (and its synonyms), and can be controlled via a command line flag (still defaults to on) #757
• Implicitly add packages to extra-deps when a flag for them is set #807
• Use a precompiled Setup.hs for simple build types #801
• Set —enable-tests and —enable-benchmarks optimistically #805
• --only-configure option added #820
• Check for duplicate local package names
• Stop nagging people that call stack test #845
• --file-watch will ignore files that are in your VCS boring/ignore files #703
• Add --numeric-version option

Bug fixes:

• stack init --solver fails if GHC_PACKAGE_PATH is present #860
• stack solver and stack init --solver check for test suite and benchmark dependencies #862
• More intelligent logic for setting UTF-8 locale environment variables #856
• Create missing directories for stack sdist
• Don’t ignore .cabal files with extra periods #895
• Deprecate unused --optimizations flag
• Truncated output on slow terminals #413

​

[Simon Michael]

Hurrah! Thank you stack devs.

[Adam Bergmark]

> stack can now reuse prebuilt binaries between snapshots.

This sounds amazing!

Thanks everyone,

Adam

On Fri, Sep 4, 2015 at 4:12 PM, Simon Michael <si...@joyful.com> wrote:

Hurrah! Thank you stack devs.

--
You received this message because you are subscribed to the Google Groups "haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stac...@googlegroups.com.
To post to this group, send email to haskel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/1DA74D2A-C2AA-462B-876F-22A1D1E6E232%40joyful.com.

For more options, visit https://groups.google.com/d/optout.

[Emanuel Borsboom]

Yes, there are plans to have stack perform the GHCJS setup as well.  The main blocker as I understand it is that GHCJS is not on Hackage yet (or following any kind of "formal" release process), but Luite announced at HIW that he intends to upload the first release soon.  Aside from that, installing GHCJS is a very different process than installing GHC from a bindist, so it's a matter of putting in the effort to develop and test it.

On Fri, Sep 4, 2015 at 10:41 AM, Michal Antkiewicz <mant...@gsd.uwaterloo.ca> wrote:

what a great release! Esp. the reuse of binaries between snapshots!

• Support added for compiling with GHCJS

I presume that stack does not assist in installing GHCJS itself as it does for ghc. Are there any plans of improving the ghcjs situation? What are the current blockers?

Thanks,

Michal