From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Jakub Kądziołka" <kuba@kadziolka.net>, guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Fri, 28 Aug 2020 15:53:15 +0200 [thread overview]
Message-ID: <87eenqq3lg.fsf@gnu.org> (raw)
In-Reply-To: <87tuwsvsiv.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 24 Aug 2020 19:54:32 +0200")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> 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.
>>
>> Are those changes part of what was merged? I get:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ guix describe
>> Generacio 153 Aug 24 2020 10:53:47 (nuna)
>> guix c687299
>> repository URL: https://git.savannah.gnu.org/git/guix.git
>> branch: master
>> commit: c6872990b51971922f3064cba54ab752fcdc1559
>> $ guix size ghc-pandoc | tail -1
>> total: 2033.0 MiB
>> --8<---------------cut here---------------end--------------->8---
>>
>> Or am I missing something?
>
> Try the “pandoc” package instead. There are now two packages:
> “ghc-pandoc” for the regular old shared library thing and “pandoc” for
> this static linking abomination.
Oh, the abomination is much nicer, thanks! (Do we actually still need
‘ghc-pandoc’?)
> (Similarly for “ghc-pandoc-citeproc” and “pandoc-citeproc”.)
>
> I should note that it doesn’t help with one case I had in mind: “guix
> pack” still includes way too much, unfortunately, so there is no impact
> on application bundle size yet.
How come? It should include exactly what ‘guix size pandoc’ shows, no?
Thanks!
Ludo’.
next prev parent reply other threads:[~2020-08-28 13:54 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
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 [this message]
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=87eenqq3lg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=kuba@kadziolka.net \
--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).