all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sat, 22 Oct 2022 10:28:05 -0400	[thread overview]
Message-ID: <87a65oszka.fsf@gmail.com> (raw)
In-Reply-To: <87r0z0cfa3.fsf@riseup.net> (Csepp's message of "Sat, 22 Oct 2022 12:39:54 +0200")

Hi,

Csepp <raingloom@riseup.net> writes:

> 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.

Yes, that's annoying.  I think it has to do with grafts; when a package
must be grafted, all its output must be available.  Grafts complicates
many things, but unfortunately they are necessary to provide timely
security updates.

I don't see a bug anymore for that one, we should try to improve things
here; feel free to report it to bug-guix@gnu.org, perhaps with a title
like "grafts cause all outputs to be downloaded".  Perhaps a solution
would be making graft derivations substitutable (currently they happen
on the local machine).

-- 
Thanks,
Maxim


  reply	other threads:[~2022-10-23 20:14 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a65oszka.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.
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.