From: Julien Lepiller <julien@lepiller.eu>
To: zimoun <zimon.toutoune@gmail.com>,help-guix@gnu.org
Subject: Re: Bug? coqide missing? (in package coq, version 8.11.2)
Date: Sat, 20 Mar 2021 22:04:28 -0400 [thread overview]
Message-ID: <538339B4-60BA-4E5E-8BA0-A21B64EFB608@lepiller.eu> (raw)
In-Reply-To: <86pmztuyxj.fsf@gmail.com>
Le 20 mars 2021 20:34:48 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi Julien
>
>On Sat, 20 Mar 2021 at 19:53, Julien Lepiller <julien@lepiller.eu>
>wrote:
>> guix size coq -> 869.7 MB
>> guix size coq:ide -> 1557.0 MB
>
>Yeah, but you have a high probability to have already have these
>dependencies.
We originally built coqide with coq itself. Because of the huge closure size, we decided to split the package in two. In this condition, the split is a win. Also, why couldn't I build a coq package on a headless server? I don't want graphics in that case :)
>
>
>> Almost twice as much, because this brings in graphical
>> dependencies. Separating packages to multiple outputs can reduce the
>> closure size of some outputs, but if you build the package, you get
>> the same number of dependencies as if there were a single output. You
>> have everything to gain if you get substitutes, and nothing to lose
>if
>> you don't have any or want to use the more expensive output.
>
>You loose what I wrote: more dependencies and less discoverability. :-)
Why more dependencies? There are either the same amount if you want coq:ide, or less than before if you don't.
>
>I agree it reduces the closure size. But it is not different to have
>different packages using inherit, right.
>
>Well, it seems a matter of taste. :-)
And a matter of what's supported upstream. I don't think coq sources let you build coqide alone very easily.
>
>Cheers,
>simon
next prev parent reply other threads:[~2021-03-21 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 6:11 Bug? coqide missing? (in package coq, version 8.11.2) yasu
2021-03-20 10:48 ` Julien Lepiller
2021-03-20 12:26 ` yasu
2021-03-20 16:39 ` zimoun
2021-03-20 23:53 ` Julien Lepiller
2021-03-21 0:34 ` zimoun
2021-03-21 2:04 ` Julien Lepiller [this message]
2021-03-21 12:06 ` zimoun
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=538339B4-60BA-4E5E-8BA0-A21B64EFB608@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
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).