unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: guix-devel@gnu.org
Subject: GHC 8.4.3
Date: Wed, 26 Sep 2018 15:34:52 -0400	[thread overview]
Message-ID: <87h8ichx2b.fsf@ngyro.com> (raw)

Hi all,

Some of you may recall that I started work on updating all of our
Haskell packages to their LTS 12 versions, and making sure they all
build with GHC 8.4.3.  I think this work is ready to be included now (on
a WIP branch, at least).  The commits exist at
<https://gitlab.com/samplet/guix/tree/wip-haskell> under the
“wip-haskell” branch.  There are 258 commits, and they have been rebased
on master (although that was a few days ago, but it should be fine
because the Haskell packages have been relatively stable).  I figure
that 258 commits is too many for guix-patches, so I’m hoping that
someone (Ricardo?) can take them from the repo linked above.  There are
about 450 packages that need to be rebuilt.

Here are some notes that you might find interesting if you rely on our
Haskell infrastructure.

  • There are 21 failing packages.  They are agda, beast, corrode,
    git-annex, ghc-aws, ghc-gnuplot, ghc-haddock-test,
    ghc-hashable-bootstrap, ghc-indents, ghc-monadplus,
    ghc-nats-bootstrap, ghc-packedstring, ghc-regex, ghc-regex-tdfa-rc,
    ghc-statistics, ghc-vector-builder, ghc-wave, ghc-xmonad-contrib,
    raincat, rapicorn, and shellcheck.  Some of these are abandoned
    upstream, but most of them just need some extra attention.  I will
    look through them (especially git-annex), but I would like the
    stability of the build farm as I do it.  (Also, help wanted!)

  • The new Haskell no longer supports the “--allow-newer” flag, so it
    has to be worked around with phases and “substitute*”.  However, I
    have introduced a “#:cabal-revision” keyword that tells the build
    system to patch in newer revisions of the package’s Cabal file from
    Hackage.  This means that we can use this mechanism whenever
    upstream has updated the dependency constraints (which is the main
    reason we made so much use of “--allow-newer” in the first place).

  • I removed “ghc-mtl” since it is now included in GHC.

If you review the patches (thanks!) you might want to know:

  • I went through all of them carefully and I sincerely hope the error
    and typo count is low!  Also, most of them are machine generated, so
    those are probably fine.

  • There are a few more interesting commits that deserve special
    attention.  There are (minor) changes to the Stackage importer,
    there’s the “#:cabal-revision” stuff, and there are some
    old/unneeded packages that I deleted.

Let me know if there is anything I can do to make these changes easier
to work with.


-- Tim

             reply	other threads:[~2018-09-26 19:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 19:34 Timothy Sample [this message]
2018-09-27 19:08 ` GHC 8.4.3 Joe Hillenbrand
2018-09-28  1:53   ` Timothy Sample
2018-09-27 19:51 ` Ricardo Wurmus
2018-09-28  9:34 ` Ricardo Wurmus
2018-09-30  8:49   ` Ricardo Wurmus
2018-09-30 11:14     ` Ricardo Wurmus
2018-09-30 13:01       ` 宋文武
2018-09-30 21:23         ` Ricardo Wurmus
2018-10-02 12:13           ` Ludovic Courtès
2018-09-30 20:46       ` Timothy Sample

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8ichx2b.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).