From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 53162@debbugs.gnu.org
Subject: bug#53162: ’guix shell ghc@8.4’ downloads ghc@8.10
Date: Tue, 11 Jan 2022 14:19:00 +0100 [thread overview]
Message-ID: <87wnj6tnp7.fsf@gnu.org> (raw)
In-Reply-To: <86lezm4l4y.fsf@gmail.com> (zimoun's message of "Tue, 11 Jan 2022 11:33:33 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Tue, 11 Jan 2022 at 11:18, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Is it a problem that the latest GHC is used to build the package cache?
>> (Apart from being surprising and suboptimal.)
>
> Functionally, it appears to be not a blocking problem. However,
> suboptimal means concretely 110+ MB of additional download; well it just
> doubles the size of the download.
Understood.
> About the surprise, if one is confident with their Guix skill, then they
> look for a bug Guix-side; if one is less confident, then they look for a
> twist in their config. In both cases, it is a diversion – let as the
> reader’s judgment if this diversion is fun or a waste of time. :-)
Yes, but that’s not very different from installing mpv and setting
downloads of ffmpeg, rav1e, rust, and all sorts of things the user
doesn’t necessarily know about.
So to me we should first look at (1) compatibility (make sure the
package cache is valid), and (2) efficiency (avoid downloading too
much).
Ludo’.
prev parent reply other threads:[~2022-01-11 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 16:15 bug#53162: ’guix shell ghc@8.4’ downloads ghc@8.10 zimoun
2022-01-11 10:18 ` Ludovic Courtès
2022-01-11 10:33 ` zimoun
2022-01-11 13:19 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnj6tnp7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53162@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.