unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Thu, 6 Aug 2020 06:45:39 -0700	[thread overview]
Message-ID: <F3E41D33-B1B9-4DDC-80F5-F473D703F3CA@asu.edu> (raw)
In-Reply-To: <87mu386vk5.fsf@elephly.net>

Hi Ricardo,


Nice! Sounds good to me. There are a couple other bits of work I’d like to see make it in.

I believe there was also some work being done to de-duplicate flags sent to gcc sent by ghc (this was the only thing keeping stack from building). 
I hope that can make it in, too!

If there is any way we can bump the default ghc to 8.8.x, that would be excellent, too.  I think something like that makes sense on staging though.

Thanks for working on it!

- John


On Aug 6, 2020, at 1:14 AM, Ricardo Wurmus <rekado@elephly.net> wrote:

Hey there,

wip-haskell contains commits that do a number of things aimed to reduce
the closure of packages:

1) make the “out” (and “lib”) output independent from “doc”
2) add a “doc” output to more packages
3) add a “static” output for all Haskell packages containing the “.a” files
4) change ghc-pandoc (and ghc-pandoc-citeproc) to use static linking

Number 1 required some smelly hackery: the generated configuration file
is edited to remove the “haddock-html” field.  One unfortunate effect of
doing this and moving the .haddock files is that there are now
complaints about unresolvable links in generated documentation.  I don’t
know if we can avoid this, but it seems like a small price to pay for
independent “doc” outputs.  (Otherwise we’d have to download huge “doc”
outputs even if we don’t want them.)

Number 3 required circumventing bug 41569.

Number 4 is by far the ugliest change of them all.  In order to
statically link packages we need to add all the “static” outputs of all
Haskell inputs *and* the “static” outputs of *their* Haskell inputs.
This is not easily accomplished, so I ended up using “package-closure”
on all direct inputs, and then filtered the result to packages with
names starting with “ghc-”.  If there was a more appropriate tool I’d
use it, but I don’t think it exists.

The result is a much reduced closure for ghc-pandoc and all packages
using it (such as R markdown).  We should probably rename “ghc-pandoc”
to “pandoc”, while we’re at it, because now the package contains the
executable.

I suppose we could change this so that “ghc-pandoc” is the usual library
package with a new “pandoc” package inheriting from “ghc-pandoc”.  I’ll
give that a try soon.

I’d be happy to hear your comments about all of this, and I’m looking
forward to merging this branch into “master” soon.

-- 
Ricardo



  reply	other threads:[~2020-08-06 13:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  8:13 merge wip-haskell? Ricardo Wurmus
2020-08-06 13:45 ` John Soo [this message]
2020-08-07 17:46   ` Timothy Sample
2020-08-07 19:53     ` Ricardo Wurmus
2020-08-09  4:29       ` Timothy Sample
2020-08-12 12:21         ` Ricardo Wurmus
2020-08-13 15:37         ` Ricardo Wurmus
2020-08-15  8:19           ` Ricardo Wurmus
2020-08-17 15:22             ` Timothy Sample
2020-08-24 15:38             ` Ludovic Courtès
2020-08-07 15:03 ` Jakub Kądziołka
2020-08-07 15:12   ` John Soo
2020-08-07 15:46     ` Jakub Kądziołka
2020-08-07 15:59       ` Ricardo Wurmus
2020-08-07 16:08         ` John Soo
2020-08-24 15:44         ` Ludovic Courtès
2020-08-24 17:54           ` Ricardo Wurmus
2020-08-28 13:53             ` Ludovic Courtès
2020-08-28 14:05               ` John Soo
2020-08-28 17:29                 ` Timothy Sample
2020-08-29 15:34                   ` Timothy Sample
2020-08-29 15:54                     ` John Soo
2020-08-07 16:27   ` Ricardo Wurmus
2020-08-07 16:55     ` Jakub Kądziołka

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=F3E41D33-B1B9-4DDC-80F5-F473D703F3CA@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).