Report currently building packages along with "Progress:" label

[develop7]

Rationale: make user feel more "in control" when waiting for these tens to hundreds of packages to be built by providing information on what is building now.

Build progress line

before

Progress: 3/74

and

after

Progress: 3/74; [Cabal-2.0.1.1|basement-0.0.4|old-time-1.1.0.3|simple-sendfile-0.2.26|stm-2.4.4.1|stringsearch-0.3.6.6]

applying this change.

Limitations: configure and copy/register stages are not covered, would require refactoring. Since these are quite fast, covering them might not worth the effect.

Note: Documentation fixes for https://docs.haskellstack.org/en/stable/ should target the "stable" branch, not master.

Please include the following checklist in your PR:

• Any changes that could be relevant to users have been recorded in the ChangeLog.md
• The documentation has been updated, if necessary.

[mgsloan]

Great! This is a step along the way to #3667

I find the use of ; and [..|..|..] a bit unprecedented, though. I think I'd prefer something more like what's described in the above issue. It'd be greatly appreciated to do the other changes in the issue.
That's not needed to get this merged, though.

To get it merged, I'd like it to read Progress 3/74: Cabal-2.0.1.1, basement-0.0.4, old-time-1.1.0.3, simple-sendfile-0.2.26, stm-2.4.4.1, stringsearch-0.3.6.6, since I think that looks nicer. It'd probably also make sense to use the pretty print stuff to give emphasis to the progress number and maybe give a style to each package name.

Edit: oops, hit the wrong button and closed.

[develop7]

@mgsloan got it, will do in a jiffy!

[develop7]

@mgsloan done! Thanks for the feedback!

[develop7]

For the record, failed build doesn't mention files I've changed

[mgsloan]

LGTM, thanks!

[snoyberg]

I just noticed this change while doing some dev and using bleeding edge Stack. THANK YOU, this is a great usability improvement 😄

[vincenthz]

looking forward to use this in production too ! small change, great usability improvement. thanks @develop7

[develop7]

Whoa, I guess I've hit a bullseye here! Thank you! Can't wait to see it in action as well! Do not feel hardcore enough to switch to nightly stack though ;)

[snoyberg]

Do it! Do it! Join us! Let your stuff break regularly, it's awesome :) FTR, my stuff _rarely_ totally breaks, and then I just `rm -rf ~/.stack` and start over.

…

On Tue, Jan 23, 2018 at 9:54 PM, Andrei Dziahel ***@***.***> wrote: Whoa, I guess I've hit a bullseye here! Thank you! Can't wait to see it in action as well! Do not feel hardcore enough to switch to nightly stack though ;) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3763 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBB6H0dQxwkza3-_CCLW7oAEgb-v6rks5tNjkLgaJpZM4RcbD7> .

[develop7]

 Let your stuff break regularly, it's awesome :)

Totally agree, though I kind of feel better having it under control :) More as a time-saver, as my day job doesn't involve Haskell at all

then I just rm -rf ~/.stack

Ya, did that maybe three times, works awesome since 1.6 though!