From: Ricardo Wurmus <rekado@elephly.net>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Fri, 07 Aug 2020 17:59:05 +0200 [thread overview]
Message-ID: <875z9u78hi.fsf@elephly.net> (raw)
In-Reply-To: <20200807154617.nvwh6g7b43tdpg5y@gravity>
Jakub Kądziołka <kuba@kadziolka.net> writes:
> On Fri, Aug 07, 2020 at 08:12:36AM -0700, John Soo wrote:
>> I would rather wait until some evidence that the closure size would be too large. Also I’m not sure propagation is necessary for dependents to find libraries or use paths from an input.
>
> Ricardo already explained that this is indeed the case.
Yes, and for the case of pandoc it’s significant. The closure of
ghc-pandoc is >3GiB right now and with the changes it’s <200MiB. This
affects lots of R packages that need Rmarkdown, and lots of bioinfo
packages.
There's no doubt that moving the static libs to their own output has a
significant impact on closure size.
--
Ricardo
next prev parent reply other threads:[~2020-08-07 15:59 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
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 [this message]
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=875z9u78hi.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=kuba@kadziolka.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).