From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: kiasoc5 <kiasoc5@disroot.org>, help-guix@gnu.org
Subject: Re: How to avoid downloading qtbase:debug
Date: Thu, 27 Oct 2022 13:03:51 -0400 [thread overview]
Message-ID: <8735b9jj0o.fsf@gmail.com> (raw)
In-Reply-To: <Y1REEq/te5C7SkLi@3900XT> (Efraim Flashner's message of "Sat, 22 Oct 2022 22:27:14 +0300")
Hi,
Efraim Flashner <efraim@flashner.co.il> writes:
> On Sat, Oct 22, 2022 at 12:39:54PM +0200, Csepp wrote:
>>
>> kiasoc5 <kiasoc5@disroot.org> writes:
>>
>> > Dear Guix,
>> >
>> > =guix shell qtbase= downloads the entire debug output of qtbase even
>> > though I didn't write down qtbase:debug. That's hundreds of megabytes
>> > of bandwith I didn't want to use. How do I avoid downloading the debug
>> > output? Is this a bug?
>>
>> I think it should be considered a bug. guix shell always downloads
>> every output of all the packages.
>
> I assume it's related to grafts:
>
> (ins)efraim@3900XT ~$ guix shell qtbase@6
> 321.1 MB will be downloaded
> qtbase-6.3.1-debug 287.7MiB 3.7MiB/s 00:01 [ ] 1.4%^C
> (ins)efraim@3900XT ~$ guix shell --no-grafts qtbase@6
> (ins)efraim@3900XT ~ [env]$
> exit
>
> Looks like it downloads all the outputs so it can perform grafts on all
> the outputs, and only then does it put just qtbase in the environment.
Yes, and this is because grafts have been marked as non-substitutable by
choice, for performance considerations. Would revisiting this choice
helps here (making graft derivations substitutable?).
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-10-27 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 1:39 How to avoid downloading qtbase:debug kiasoc5
2022-10-22 10:39 ` Csepp
2022-10-22 14:28 ` Maxim Cournoyer
2022-10-22 15:37 ` Csepp
2022-10-22 15:28 ` Tobias Geerinckx-Rice
2022-10-22 19:27 ` Efraim Flashner
2022-10-27 17:03 ` Maxim Cournoyer [this message]
2022-11-18 16:37 ` Ludovic Courtès
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=8735b9jj0o.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=kiasoc5@disroot.org \
--cc=raingloom@riseup.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.
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).